Database Info

Note 3 - Is It Possible to Manually Install Marshmallow

I previously rooted my Note 3 (I do not remember what technique I used). I also disabled OTA updates using NoBloat Free. I have since removed root using SuperSU but the normal method for checking for updates does not work. I also tried to clear the Google Services Framework as well as the "*#*#" trick.
Does anyone know what I need to do in order to get the system update functionality working again? If not, is there a way to to a manual OS update? I'm currently running 4.4.2 and I would like to upgrade to the latest version of Marshmellow. Here are some other specs - Baseband N900PVPUCNAB, Kernel version 3.4.0-533717. Any suggestions?

As an update, I just performed a factory reset....still nothing. Nothing happens when I click on the Update option. The same goes for "Update PRL" and "Update Profile."

There is no stock MM for the note 3?...AFAIK Note 3 ended with LP. There are a couple CM based roms on MM.

Pigeon Flipper said:
There is no stock MM for the note 3?...AFAIK Note 3 ended with LP. There are a couple CM based roms on MM.
Click to expand...
Click to collapse
Thanks but I have no idea what you wrote.

There is no Marshmallow for the note 3. Samsung never put it out for us; they left us of at lollipop. However if you re root you can install Marshmallow from a third party. Such as Cynagenmod.
So long story short if you want OTA updates on the note 3 you are stuck of at LP. If you want MM you must root and flash custom ROM.

Any UK users got Android Pay to work?

I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.

No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.

captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?

themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.

Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.

I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper

Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170

I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180

Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out

Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320

gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...

bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install

Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8

Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks

I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app

Samsung Galaxy S7 Edge Nougat Beta Program

So how many of you got into the program. Was recently announced that Samsung will be letting users beta test Nougat on the S7 and S7 Edge. Will go live on Nov 9th!

Where can I download the app? Tried to search it at samsung app store and couldn't find it
Sent from my SM-G935T using XDA-Developers mobile app

NirAndroid said:
Where can I download the app? Tried to search it at samsung app store and couldn't find it
Click to expand...
Click to collapse
www.apkmirror.com/apk/samsung-electronics-co-ltd/galaxy-beta-programme/galaxy-beta-programme-1-0-00-release/galaxy-beta-programme-1-0-00-android-apk-download

An error has occured on this service.
Its giving me the error wat shud i do????

Careful!
They might update the bootloader again preventing the engineering kernel from being used thus no root.
Install Nougat and you might be stuck. At least for a while.

I wonder if you could talk them into root access for advanced debugging... Or it could be a massive social engineering attack on the S7 power users... Regular Joe's won't sign up for this.. Only the ones whom seek root... And I can see this update havins some sort of "kill switch" in it to remotely kill the kernel if it is altered from original code that is paired to the imei or some other hard coded descriptor.. That is all it would take for a permbanhammer..... So I see Samsung "offering up beta Nougat to test" when it wipes out the rooting problem before the **** is released. OR... It is going to have Windows 10 level tracking in it that literally records and sends all you do back to Samsung.. I would be interested to see pcap info from the device on a network. Samsung is just watching all the steps the SU's take to breach root at the kernel level and allows it to happen, while they are at shop fixing the **** in real time....
It's what I would do.... If I were a square...

Binary100100 said:
Careful!
They might update the bootloader again preventing the engineering kernel from being used thus no root.
Install Nougat and you might be stuck. At least for a while.
Click to expand...
Click to collapse
Almost certainly. But would the eng_boot even work? Does nougat not run a different kernel revision?

billydroid said:
Almost certainly. But would the eng_boot even work? Does nougat not run a different kernel revision?
Click to expand...
Click to collapse
Very unlikely the kernel would work.
So you'll have to choose either root or Android 7.

Still getting server error

The app is live in galaxy apps. Still get server error though
Sent from my SM-G935T using Tapatalk

Same to as I get server error.

I got the app but getting server error.

Server error here also
Sent from my SM-G935T using Tapatalk

Server error here as well. I imagine they are spreading things out to ease server load.
In the meantime, here are beautiful screenshots of the S7 running Nougat under the beta:
http://www.sammobile.com/2016/11/09...ugat-beta-running-on-a-galaxy-s7-screenshots/

It's working now, I'm registered..... I'll let you know when the update comes...

Just registered to. Wondering though If this is just to assemble a waiting list for later or if they actually plan to start updating devices today or tomorrow.
Sent from my SM-G935T using Tapatalk

just got registered via the app, lets see what happens next...

are you guys on official Tmobile firmware or the unlock firmware. I'm on the unlocked firmware and getting server error. According to this article: unlocked Galaxy S7 or S7 edge variants won't be included in the beta program - See more at: http://www.techtimes.com/articles/1...ow-to-get-the-update.htm#sthash.lhPDWGM2.dpuf

Xpiatio said:
are you guys on official Tmobile firmware or the unlock firmware. I'm on the unlocked firmware and getting server error. According to this article: unlocked Galaxy S7 or S7 edge variants won't be included in the beta program - See more at: http://www.techtimes.com/articles/1...ow-to-get-the-update.htm#sthash.lhPDWGM2.dpuf
Click to expand...
Click to collapse
I switched from the U version for this reason exactly. We were all getting the server error, but I do not think it will be available to install on the U firmware.

I am on official Tmobile software and got registered. I have not seen a download yet though.
It says to: Click the "Software Update" menu, setting > Device Information > Download Updates
But I am not seeing that functionality yet. It looks like the app will get a server side update that will setup a few new items, like: Error reports menu, Suggestion Menu, and a Download Menu.

Is there a way to reconnect to Android 7 Beta?

I was accepted on the official Beta and installed Nougat on my G7
Due to some issues I did a hard reset and in the process seem to have been 'deregistered' from the Beta. Opening the Beta app shows a 'Register' link in the 'more' menu and pressing that says the Beta is fully subscribed; on the bottom of that screen there is a 'Register' link as opposed to 'Derisgister' that was originally there.
So it seems I am stuck on the version of A7 that is on the device- Software Update says I have the latest version.
Is there a way to re-enable the Beta registration as I was on it initially?

You need to flash latest BTU and if you registered before it should be okay because it's linked on your sammy account.
So after flashing and login you should receive a update.
Sent from my SM-G930F using XDA-Developers mobile app

Thanks Johnny, but the problem seems to be that I have become 'unregistered' so if I return to the Android 6 BTU I won't get the A7 update.
Think I'll just have to wait it out!

IF you flash manually via Odin without being able to register, do you get updates of the betas via OTA even if you aren't registered in the beta?

donalgodon said:
IF you flash manually via Odin without being able to register, do you get updates of the betas via OTA even if you aren't registered in the beta?
Click to expand...
Click to collapse
Nope, OTA only if you are registered

Question Q: What to do with ATT Snapdragon SM-S908 stuck on OneUI 5.0 beta 1? (Re-enable OTA)

Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?

*I do not have any backups from Android 12 stable.

You tried flashing official firmware for U device right? You were using CSC file or HOME_CSC to preserve data?
Going back from beta to stable means wiping data, phone will factory reset when you flash back the stable firmware and you should use the CSC file (not HOME_CSC)

Yeah... I know how to operate Odin3... It literally says right there I tried flashing multiple stable builds and each time it fails with AUTH error. Tried HOME and regular CSC....

I have the same phone. I have not gone back to stock U firmware from beta. But I have gone from beta to stock U1 firmware. I believe once you go back to stock U1 Android 12. You can flash back with Odin not patched to U firmware.

zlib1 said:
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
Click to expand...
Click to collapse
Any chance you still have the flashing zip file for beta 1 s908?
The link for beta 1 in this post isn't working
If you do can you send it to me please?
Thanks