Database Develop

[Q] New official JB release?

Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.

This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app

alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.

File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,

I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc

This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.

sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.

It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.

It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve

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

I have decided to create this thread due to extraordinary success of my unofficial builds that I recently put in this thread
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
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

_alexndr said:
I have decided to create separate thread due to the extraordinary success of my unofficial compilation that I recently put in this thread
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
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
Click to expand...
Click to collapse
thanks! it works perfectly

I'm glad you decided to start a new thread. The other one is just TOOO LONG! Great work, keep it up You rock!

i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking

Racinghart91 said:
i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking
Click to expand...
Click to collapse
because it can happen that in your country the latest firmware is available 1 month after another lucky country (or operator)

Racinghart91 said:
i dont understand it... why would we flash this instead of the original firmwares on sammible ?
just asking
Click to expand...
Click to collapse
Another thing is that you probably just can't flash original BOD2 firmware due to different partition layout than in case of typical, unbranded phone. Read here for more info:
http://forum.xda-developers.com/showthread.php?p=60603630

Great work, tried to install the BOD2 from Sammobile yesterday but obviously ran into the EXT4 error.

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.

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 said:
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.
Click to expand...
Click to collapse
Didn't work for me despite B0C7 appearing to be earlier than B0D2.

StevePritchard said:
Didn't work for me despite B0C7 appearing to be earlier than B0D2.
Click to expand...
Click to collapse
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.

RandyKaoss said:
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.
Click to expand...
Click to collapse
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.

StevePritchard said:
I'm struggling to see how it can be Samsung's fault when all the other players seem to work just fine.
Click to expand...
Click to collapse
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?

RandyKaoss said:
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?
Click to expand...
Click to collapse
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.

StevePritchard said:
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.
Click to expand...
Click to collapse
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!!>

Hi Alex,
Any chance of a N910FXXU1BOE2 (0x0) Repacked Firmware?
This is exciting, all these NEW firmware being released.

luckyluis said:
Hi Alex,
Any chance of a N910FXXU1BOE2 (0x0) Repacked Firmware?
This is exciting, all these NEW firmware being released.
Click to expand...
Click to collapse
BOE2 is an earlier build than BOD2, the changelist is less than BOD2. The BOE2 seems to be just a naming convention.

Batfink33 said:
BOE2 is an earlier build than BOD2, the changelist is less than BOD2. The BOE2 seems to be just a naming convention.
Click to expand...
Click to collapse
You are right that the changelist seems the same as B0C5, but the build date is much later - I'm wondering if the changelist for B0E2 is just a typo, and it is a newer release?

When we flash this rom then we have official update over OTA?
EDIT-I found answer sorry.

OP,
have you plans to repack with BOC4 instead of BOC3?
Cheers.

Samsung Galaxy S5 G900f Android 6.0.1 Marshmallow beta - Screnshoot & Video

New Update Samsung Galaxy S5 Android 6.0.1 Marshmallow
*** Mod edit ***

MixTech said:
*** Mod edit ***
Click to expand...
Click to collapse
How have you received the update? Via OTA? What was your latest firmware? What CSC?
Thanks in advance![emoji2]
EDIT:
You have 1CPB4 firmware but Sirocco's one (publied version in XDA) is 1CPB2.. so can you answer my questions? I'm excited to know..! Thanks. @MixTech

All I see is Marshmallow's additions and the launcher/app icons, noting more! Kinda disappointed :/ but that sammy has been doing all these years.

i received this update via OTA and csc BTU

MixTech said:
i received this update via OTA and csc BTU
Click to expand...
Click to collapse
Have you already rooted the rom?
Anyway I mention some devs more expert than me to show this to them: @BlackMesa123 @firefds @komarov27 @eeausli @geiti94
In this thread the OP's author has received via OTA Marshmallow update 1CPB4, (Sirocco's one is older than this ~1CPB2~)...
Can this firmware help the S5 development?
(I haven't mentioned you to disturb you, but I have mentioned you because I think you are more expert than me and maybe you haven't seen this thread that maybe can become important..)
Thanks in advance!

lucadalba said:
Have you already rooted the rom?
Anyway I mention some devs more expert than me to show this to them: @BlackMesa123 @firefds @komarov27 @eeausli @geiti94
In this thread the OP's author has received via OTA Marshmallow update 1CPB4, (Sirocco's one is older than this ~1CPB2~)...
Can this firmware help the S5 development?
(I haven't mentioned you to disturb you, but I have mentioned you because I think you are more expert than me and maybe you haven't seen this thread that maybe can become important..)
Thanks in advance!
Click to expand...
Click to collapse
If OP want to make system dump will be great but seems the same as Sirocco one (same build CPB only final number change) but maybe something changed

midi_1996 said:
All I see is Marshmallow's additions and the launcher/app icons, noting more! Kinda disappointed :/ but that sammy has been doing all these years.
Click to expand...
Click to collapse
I am on CB2 (6.0.1), and it is a lot smoother than lollipop, it has all MM feature (like doze), nice animations, no more lag button on multitasking, what do you missing?

A dump would be great. It seems the current samsung build is CPB7 (according to this twitter https://twitter.com/koonsj/status/702359062663528448 in Korean), however CPB4 has to be better than CPB2
The most important would be to have a dump of the stock recovery partition, as it is currently lacking for the dump sirocco did.
Ps : if you want to make a system dump please do it BEFORE rooting, to keep the kernel stock and allow us to flash it while keeping knox 0x0!

alexbelgium said:
A dump would be great. It seems the current samsung build is CPB7 (according to this twitter https://twitter.com/koonsj/status/702359062663528448 in Korean), however CPB4 has to be better than CPB2
The most important would be to have a dump of the stock recovery partition, as it is currently lacking for the dump sirocco did.
Ps : if you want to make a system dump please do it BEFORE rooting, to keep the kernel stock and allow us to flash it while keeping knox 0x0!
Click to expand...
Click to collapse
We can't make dump without rooting the phone and BTW Recovery isn't important we can flash stock 5.0 one too

BlackMesa123 said:
We can't make dump without rooting the phone and BTW Recovery isn't important we can flash stock 5.0 one too
Click to expand...
Click to collapse
Well Sirocco provided us with a twrp backup of the kernel before rooting. That way, Alxndr was able to create a devbase cpb2 that can be flashed while keeping Knox 0x0. He combined the kernel from the twrp backup with the system from the adb dump (that contains a modified kernel due to rooting)
I trust you that the 5.0 recovery works but (I don't know why) alexndr didn't include it in his devbase so it wasn't a stock 6. 0 recovery.

alexndr didn't include a 5.0 recovery as there is no point in doing so. if you want to keep knox 0x0 and because of this flashing through flashfire, then you don't need to flash a 5.0 recovery since you most likely will already have one.
creating a dump of the recovery partition is not possible. for this you would need root for which in return you would need to flash a custom recovery.

Dial *#1234# please
Could you dial this code and tell us what's written?
Maybe SamFirm would work.

[SECURITY UPDATE] ALE-L21C432B6(09|10) [Single|Dual SIM]

DOWNLOADS:
Dual SIM (B610):
OTA MD5:677B13E573128E27A3D7AC552F92D366
FULL MD5:A2AFE2F11AB7D186947A0738FC0FECDD
Single SIM (B609):
OTA MD5:19B35E6C8F6E654809B8154EF4C4936B
FULL MD5:3A1651B86CAB6B27E82F49B67271D49F
CHANGELOG:
This update improves system security with Google security patches.
[Optimizations]
Improved device security with Google security patches.
[Update notes]
1. This update will not erase your personal data, but we recommend that you back up any important data before updating.
2. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
Click to expand...
Click to collapse
You can always find new updates with Huawei Firmware Finder, or on this page.
INSTALLATION:
OTA: You need to have stock recovery. you will extract the UPDATE.APP from the .zip and put that in a folder called "dload" in your phone's SD card. Now you can either:
Dial *#*#2846579#*#* in the stock phone app, and go Software Upgrade > SDcard upgrade or
Shutdown the phone, and then hold POWER, and both the VOL buttons until the EMUI update starts
FULL:
You can flash the update.zip in TWRP. It will show a small error but it's fine.
You can also extract the UPDATE.APP and get the partitions boot, cust, system using Huawei Update Extractor (usage instructions in the forum), then flash with fastboot through an unlocked bootloader (HOW DO I DO THAT?)
If you have stock recovery you can extract the UPDATE.APP from the .zip and put that in a folder called "dload" in your phone's SD card. Now you can either:
Dial *#*#2846579#*#* in the stock phone app, and go Software Upgrade > SDcard upgrade or
Shutdown the phone, and then hold POWER, and both the VOL buttons until the EMUI update starts

Huawei can't understand that we don't want only security patches...

If I remember correctly the higher build number used to be Single SIM. Did they changed the build numbering?

D1stRU3T0R said:
Huawei can't understand that we don't want only security patches...
Click to expand...
Click to collapse
Yes, I want android 8.0.0, too

D1stRU3T0R said:
Huawei can't understand that we don't want only security patches...
Click to expand...
Click to collapse
you're right, only security patches.. We want more modifications of the ROM, I go well with the one of Persona78 is a crack, a greeting.

PErsonally I'm really glad that they keep the patches coming. I'd like to get more than that for sure, but Huawei can't invest on this phone anymore... It's important that they still provide these updates. We have custom ROM development now

JpegXguy said:
PErsonally I'm really glad that they keep the patches coming. I'd like to get more than that for sure, but Huawei can't invest on this phone anymore... It's important that they still provide these updates. We have custom ROM development now
Click to expand...
Click to collapse
Seeing it from your point of view you're right.
Already takes 2 years of support and that is a lot for a mid-range mobile.

Yes, custom rom support now. Great! Hope the phone has a long life and we can get maybe android 8.0 working

allrightlite said:
Yes, custom rom support now. Great! Hope the phone has a long life and we can get maybe android 8.0 working
Click to expand...
Click to collapse
What? What are you talking about?

D1stRU3T0R said:
What? What are you talking about?
Click to expand...
Click to collapse
That we have stable android 7.1.2 roms which are very fast and stable and maybe the phone survived one more step. But android 8.0 is not really a big step, or? But 7.1 was important. Very happy with it

This cannot include security patches for September. It's impossible. I talked to Google, they said that this can't be. I don't know if Huawei does anything at all in these patches. I don't think so.

Vinnipinni said:
This cannot include security patches for September. It's impossible. I talked to Google, they said that this can't be. I don't know if Huawei does anything at all in these patches. I don't think so.
Click to expand...
Click to collapse
Would this mean that Huawei's updates were just fake numbers in security patches , and Google's late this month spotted Huawei ? LOL ???

salembream said:
Would this mean that Huawei's updates were just fake numbers in security patches , and Google's late this month spotted Huawei ? LOL ???
Click to expand...
Click to collapse
Yeah, they are fake every month. Google releases the patches on the first Tuesday every month.

The sizes ARE different to a degree that suggests changes. Surely last month's patches are included though like August in the "September" patch

Vinnipinni said:
This cannot include security patches for September. It's impossible. I talked to Google, they said that this can't be. I don't know if Huawei does anything at all in these patches. I don't think so.
Click to expand...
Click to collapse
You talked to google? But you are maybe right. Another person here in xda forum has tells that was possible to infect the device although all fixes which should be included. So, what is the security patch level worth on P8 Lite stock rom? That's the big question. Maybe the patches will be included just partially? Maybe it's a huawei own security patch level?
JpegXguy said:
The sizes ARE different to a degree that suggests changes. Surely last month's patches are included though like August in the "September" patch
Click to expand...
Click to collapse
Ok, then could it be that's a huawei own patch level

With the b610, September 1st patch. And latest version of Magisk 13.3 works perfectly and ALL in green.
Con la b610, parche del 1 de Septiembre. Y última versión de Magisk 13.3 funciona perfectamente y TODO en verde.

I have downloaded from Firmware Finder b610. Once installed my device says it's b609 but i have dual sim one

Of course they released just a patch! Why would they release EMUI 5 or at least EMUI 4.1(non-vodafone) for this device?:good:
Oh well... at least we get security patches...

I "only" want these (being possible):
Android 6.0.1(idc if it's emui 4.1)
Latest GPU drivers(and maybe higher gpu frequency(btw, Huawei support said they can optimize gpu, but they won't raise its mhz) or cpu freq)
Latest kernel, 3.10.107

Qu1ckR00t on Samsung devices

So, for those who know don't know already, a new zero-day (CVE-2019-2215) was recently found that applies to a majority of devices that run Oreo and higher, and a PoC application created by Grant Hernandez has been made to demonstrate the potential of this exploit when it comes to rooting. The code of this PoC application has been released onto GitHub and you can check it out in the links below, and maaaaaybe this means that the code can be customized to work on Snapdragon Samsung devices (no idea about Exynos) as this has been tested only on Pixel 2 devices, and in my own attempt in running the app, the process hangs after a few seconds. Sadly, there are a good amount of downsides with this PoC, mainly that Magisk is installed in core-only mode, and installed without a patched boot image. According to Grant, installing other Magisk environments and or updating it can possibly cause DM-Verity and you'd need to do a clean install.
I just wanted to share this with you guys, maybe we can utilize this for the greater good, and hopefully get some stuff going for Samsung devices with this as the base.
PS: The October security update patches this vulnerability, so if you already updated, yikes.
Related links
https://github.com/grant-h/qu1ckr00t
https://github.com/kangtastic/cve-2019-2215/blob/master/cve-2019-2215.c

The PoC of Hernandez manipulates kernel data structures, the user process credentials, that are protected by Samsung real time kernel protection (RKP). Normally, the PoC should therefore not work on Samsung devices, or am I wrong with that?
The original PoC was reported to work on S8 and S9. But i fear this was only due to the PoC did not trigger RKP. Will have a look at the original PoC, to assess that ...

i think the Samsung Knox version is decisive. This document states, RKP only protects kernel data structures on selected devices: (search for Real-time Kernel Protection (RKP))
In the 2018 version this comment is missing, indicating newer Knox versions protect kernel data structures on all devices: (Search for Knox Deep Dive: Real-time Kernel Protection (RKP))
In this case the PoC of Hernandez will not work.

Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks

antintin said:
Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks
Click to expand...
Click to collapse
It's kinda active here but I wouldn't hold my breath waiting for help with an LG in a Samsung note 9 forum tbh.