Psa: DO NOT TAKE OTAs after updating to kitkat leak (nc2)

Harleydroid

Harleydroid

Senior Member
Jul 18, 2013
1,911
967
0
The Fort
Apr 26, 2014 at 8:24 AM
williamweaver said:
I odined from stock mje to the sextape leak. I didn't really care for it, so I odined back to mje. Worked fine for me. I did use a pit file to reformat with the mje.

Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
That's some awesome info my friend. So anyone that did the sxtp 4.4.2 odin leak can Odin back to MJE and root then flash the rooted kit Kat beans builds. Thanks for your reply.
 
Borderpatrol1987

Borderpatrol1987

Senior Member
Dec 5, 2012
264
58
0
CIncinnati
Apr 26, 2014 at 3:44 PM
DrPhant0m said:
The only problem I've come across so far is that Google Wallet Tap to Pay doesn't work... but that seems to be common to everyone that installed the leak, not just me. There seems to be an explanation for it... Something about "NXP Controller" and "HCE" being supported in 4.4.3 natively. (Don't quote me on this... I don't understand what I'm saying) A link was posted here, to explain... http://forum.xda-developers.com/showthread.php?t=2573842 (I didn't understand what was here, either.) :eek:
Click to expand...
Here's why it won't work yet. When Google wallet first came out it used a physical secure element chip on the phones to encrypt your credit card info. This didn't play nice with ISIS. Verizon/Att/T-Mobile didn't like this and blocked it.

Google didn't take this lying down and came up with a other solution. A Software based secure element. In order for this to work, they needed Host Card Emulation (HCE). NCI, one of two manufacturers provided the necessary programming for it to work.

Our phones have NFC chips provided by NXP. NXP has not yet released the programming needed to get the HCE to work into AOSP, thus we don't have tap and pay at this current time

Now to further frustrate everyone. There are a few phones that have NXP and working tap to Pay. Those are the Google play devices. We have been trying to decompile the code and pull the necessary code out. But that's not as easy as it sounds.

So, sit tight and wait for 4.4.3 and hopefully we can make it work.

Sent from my SM-N900V using xda app-developers app
 
  • Like
Reactions: LillieBennett
DrPhant0m

DrPhant0m

Senior Member
Oct 21, 2010
928
271
93
Apr 26, 2014 at 4:04 PM
Borderpatrol1987 said:
Here's why it won't work yet. When Google wallet first came out it used a physical secure element chip on the phones to encrypt your credit card info. This didn't play nice with ISIS. Verizon/Att/T-Mobile didn't like this and blocked it.

Google didn't take this lying down and came up with a other solution. A Software based secure element. In order for this to work, they needed Host Card Emulation (HCE). NCI, one of two manufacturers provided the necessary programming for it to work.

Our phones have NFC chips provided by NXP. NXP has not yet released the programming needed to get the HCE to work into AOSP, thus we don't have tap and pay at this current time

Now to further frustrate everyone. There are a few phones that have NXP and working tap to Pay. Those are the Google play devices. We have been trying to decompile the code and pull the necessary code out. But that's not as easy as it sounds.

So, sit tight and wait for 4.4.3 and hopefully we can make it work.

Sent from my SM-N900V using xda app-developers app
Click to expand...
I had it working running CM11 on my S3. To the best of my knowledge, that is AOSP, 4.4.2
 
U

user32

Senior Member
Nov 17, 2007
56
2
0
Apr 26, 2014 at 4:27 PM
Hopefully I'ts ok to ask such a question but I'm on the verge of getting a note 3 from clist so I was wondering if someone ca assist me on what to look for and avoid as far as current roms. I wanna ensure the previous user didn't take the update that would lock me down, so to speak, but I'm not sure of the past and or current build to avoid. Any help would be greatly appreciated.
 
DutchDogg54

DutchDogg54

Retired Forum Moderator
Aug 16, 2011
2,472
2,866
0
Des Moines, IA
Apr 26, 2014 at 4:36 PM
user32 said:
Hopefully I'ts ok to ask such a question but I'm on the verge of getting a note 3 from clist so I was wondering if someone ca assist me on what to look for and avoid as far as current roms. I wanna ensure the previous user didn't take the update that would lock me down, so to speak, but I'm not sure of the past and or current build to avoid. Any help would be greatly appreciated.
Click to expand...
Honestly, I haven't heard of an OTA rolling out yet so I wouldn't be worried about getting a device that has accepted that & can't go back or be rooted. The OTA could come at any time but I'm sure you'll hear about it here quickly so until then any out on the market should be able to be rooted, etc.

Of course use common sense on things like bricked devices, cosmetic damage, etc.

Sent courtesy of my Note 3 & XDA Premium
 
  • Like
Reactions: user32
DrPhant0m

DrPhant0m

Senior Member
Oct 21, 2010
928
271
93
Apr 26, 2014 at 5:51 PM
user32 said:
Hopefully I'ts ok to ask such a question but I'm on the verge of getting a note 3 from clist so I was wondering if someone ca assist me on what to look for and avoid as far as current roms. I wanna ensure the previous user didn't take the update that would lock me down, so to speak, but I'm not sure of the past and or current build to avoid. Any help would be greatly appreciated.
Click to expand...
Some stuff to consider is what root method can be used, depending on the firmware installed... and whether or not you care if the knox flag has been set. The latter will likely only apply if you have enterprise security concerns... which is unlikely if you're buying the phone on craigslist.

As for the root method... There is no unrootable version of the Verizon phone, since the kit kat update has not been officially pushed. Find the "Universal Root De La Vega" thread for which versions are supported by that method. You may have to use Kingo or vRoot... but these methods have had a sketchy past, so proceed with them only if you understand what they are (and more importantly... what they are NOT).

Ideally... you would want to find a Note 3 with the MI9 firmware version on it (the initial release), and it would already be rooted via the original root de la vega method. That setup worked great for me in getting onto the leaked, pre-rooted kitkat build.

Consider checking Swappa, too. You can get more information without having to hassle the craigslist sellers, who, as I have found out first-hand... are often surprisingly unwilling or unable to answer questions about their own devices that they are selling. Also... in one case, a seller was selling 100 pain pills and a Note 3 that they "found" and did not want to split the two to sell separately. Weird, huh?

Good luck!
 
  • Like
Reactions: user32
shawn01

shawn01

Senior Member
Aug 13, 2010
344
30
0
Apr 26, 2014 at 6:10 PM
Hey I've been having problems downloading the deodex version it says 1.57 gb but I thought it was 1.6.. can anyone confirm? Thanks.

Sent from my SM-N900V using Tapatalk
 
tpike

tpike

Senior Member
Jan 31, 2011
1,083
200
0
Apr 27, 2014 at 12:22 AM
Looking forward to kexec :) ktoones kernel was great on my s3. This is a great way thing to tide me over until my s5 gets rooted

Sent from my SM-N900V using Tapatalk
 
G

GuestK00143

Guest
Apr 27, 2014 at 7:10 PM
Everyone better freeze these two as well... Verizon tried pushing a OTA on me a few minutes ago through this.
View attachment 2712210

EDIT.. Thankfully it won't download from what Beans took out but freeze them anyways if you want to get rid of the annoying popup.
 
Last edited:
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone