Database Develop

Firmware updates for the FE

Just received the August security patch.
Takes a while for the restart.

jah said:
Just received the August security patch.
Takes a while for the restart.
Click to expand...
Click to collapse
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.

cortez.i said:
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.
Click to expand...
Click to collapse
My Note FE is my prime device. Not keen to experiment too much.

ROOT?!
cortez.i said:
do you intend to keep your device stock/unrooted? i'm reluctant to take the update for fear of losing root.
Click to expand...
Click to collapse
I haven't found a reliable method of rooting my N935L model. I am dying to root it. Can you link me?

ClrDaLane said:
I haven't found a reliable method of rooting my N935L model. I am dying to root it. Can you link me?
Click to expand...
Click to collapse
i followed the same process to install the latest version of TWRP for the Note 7 and flash the latest version of SR1-SuperSU-v2.82-SR1-20170608224931.zip. that's how i rooted my 935K. so far, this process still works with the latest AQG6 release which is available from updato.com. NOTE: if you flash the full OEM ROM via Odin, be sure to backup your internal storage; i had to format data after flashing the OEM ROM.

cortez.i said:
i followed the same process to install the latest version of TWRP for the Note 7 and flash the latest version of SR1-SuperSU-v2.82-SR1-20170608224931.zip. that's how i rooted my 935K. so far, this process still works with the latest AQG6 release which is available from updato.com. NOTE: if you flash the full OEM ROM via Odin, be sure to backup your internal storage; i had to format data after flashing the OEM ROM.
Click to expand...
Click to collapse
Good to know. Do we still have adhell? I expect Google will want to see that app spiked ASAP. Also, whether you update OTA or flash the full firmware, you will need to format data to get root. I long ago routined this process so that it takes about an hour all told.

zamzenos said:
Good to know. Do we still have adhell? I expect Google will want to see that app spiked ASAP. Also, whether you update OTA or flash the full firmware, you will need to format data to get root. I long ago routined this process so that it takes about an hour all told.
Click to expand...
Click to collapse
correct, the format data requirement is a bit of a pain; however, i keep very little important "stuff" on internal storage and back up my external and internal storage once a week.

Have updated by flashing stock to clear Knox first. Adhell still works. Just as well: cannot install TWRP, neither Exynos variant. Not such a pain while adhell keeps ads out and allows me disable copious junk. Still, am I doing something wrong? Odin installs always a success (four times so far). Any other reports?
Perhaps we need a device specific variant now...

zamzenos said:
Have updated by flashing stock to clear Knox first. Adhell still works. Just as well: cannot install TWRP, neither Exynos variant. Not such a pain while adhell keeps ads out and allows me disable copious junk. Still, am I doing something wrong? Odin installs always a success (four times so far). Any other reports?
Perhaps we need a device specific variant now...
Click to expand...
Click to collapse
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.

cortez.i said:
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.
Click to expand...
Click to collapse
1. Probably clumsily expressed. I flashed the original AQFE stock to get out of root then updated that. I was dloading the AQG6 firmware at that time but rather than wait (when I could have flashed that instead) I went ahead.
2. Usually I flash TWRP, allow the restart, close down and reboot into recovery-TWRP. Didn't work this time - is this a significant change? Followed your method, which worked - except perhaps to underline that the device should remain connected to the PC while closing it down (otherwise it will automatically reboot). Thanks for taking the trouble to give detailed instructions.

Just received an update

jah said:
Just received an update
Click to expand...
Click to collapse
THX! :good:
I manually update,been a while since I last looked:
Just checked my Note FE & got the same update on the SK Telecom version.

why i did't reveice?
i use note fe too

Whats new?
Wysłane z mojego SM-N935K przy użyciu Tapatalka

https://www.sammobile.com/news/galaxy-note-fan-edition-updated-december-security-patch/
Samsung starts rolling out December patch for the Koreans Note FE users.

RicePlay33 said:
https://www.sammobile.com/news/galaxy-note-fan-edition-updated-december-security-patch/
Samsung starts rolling out December patch for the Koreans Note FE users.
Click to expand...
Click to collapse
This is an old one I guess. Found this new firmware on Sammoblie on 2017/12/13 but I cannot flash it at the moment.
Can anyone try it? Hope it will bring bixby voice to our Note Fe

Got my K-version updated through OTA, no Bixby.

cortez.i said:
what do mean by flashing stock to clear Knox first? and you flashed build N935KKKU3AQG6? i had no problem flashing twrp-3.1.1-0-gracelte.img.tar (not the Korean version twrp-3.1.1-0-graceltekor.img.tar) using Odin 3.12. reboot to Download mode and be sure to untick Auto reboot. next load twrp-3.1.1-0-gracelte.img.tar to the AP slot, flash and when complete, reboot to recovery. my method is to hold the down-volume and power key until the phone turns off, then press and hold the up-volume key, the power key and the the home key until the device boots to TWRP.
Click to expand...
Click to collapse
That's a bit unrelated but I was wondering : how did you managed to show your carrier name (AT&T) in the status bar ?
I've always tried but other than with root capabilities I've never been able to display it.

Just received January security patch.

Me too!
Sent from my SM-N935F using Tapatalk

Note 8 T-Mob downgrade after update to Pie Beta

Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
logs from odin? Or any error code or anything?

Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.

pzzamakr1999 said:
Nothing from Odin at all. Odin registered it as a Pass. And I'm unsure how I would pull logs from the phone. Once the "Error!" appears during update, the phone will enter a bootloop unless I hold down the power button to enter Recovery. I was able to successfully enter Recovery, reinstall the Pie Beta Update from my SD card, and the phone works fine again. However, I do use Samsung Pay, and I've noticed that service has suffered considerably, so I'd like to go back to Oreo for the moment.
Click to expand...
Click to collapse
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry

pzzamakr1999 said:
Hey All, any chance of getting a step by step to downgrade back to CRK1 or latest Oreo build. I attempted to do so, using the firmware from SamMobile, and it failed during the "Updating System" step with an "Error!" message at 32%. Odin had registered a pass. I installed the Ap, Bl, Cp, and the clean CSC. There was only 30ish percent of battery remaining if that would make a difference. I also had the December update installed when I updated to the DLR6 version.
Click to expand...
Click to collapse
Which ODIN are you using? Make sure you're using the modded 3.13.1. Try this: Uncheck the auto-reboot option on ODIN. Flash the Oreo firmware and let it finish. Once it's done, manually reboot into recovery and perform a factory reset. Then boot into the OS.
ScaleneVirus288 said:
I wouldnt be suprised if samsung locked going back same what they did with nougat/oreo . I cant help u, sry
Click to expand...
Click to collapse
That only happens when they update the bootloader version. It has nothing to do with the OS version. The Pie leaks are still on the v5 bootloader.

Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
Also check the USB port, use the older USB port this has happened to me or PC and see the phone is probably not compatible with newest USB port....
Sent from my SM-N960U using Tapatalk

pzzamakr1999 said:
Ok, I will give that a try. I will admit, I'm really enjoying Pie, and its user interface tweaks. I just may forego Samsung Pay and wait until Pie is out of Beta.
On that note, is there any way to install the old radio and use the Oreo radio rather than the one bundled with Pie, assuming that Pie has a new radio bundled. Because that is kinda the Beta killer.
And last comment, once Pie is out of Beta, what will I have to do to upgrade to the "Release" version. Will it be an Odin install, or should an OTA take care of it?
Click to expand...
Click to collapse
What issues are you having with Spay? It seems to work for everyone else, me included.
No, you can't flash a different radio.
Not sure yet what will be required when when the official drops. Won't know until it drops.

So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.

pzzamakr1999 said:
So the Pay app opens fine, and it authenticates the card without issue. It will also allow me to put my fingerprint in, and then have the countdown start. However, it doesn't seem to enable the mag spoofer or the nfc chip, and when put next to a mag reader or Pay system, nothing happens. The countdown will continue, and will restart if I ask it to. But again, the phone doesnt seem to do anything.
Click to expand...
Click to collapse
Weird. I'll have to try it. I thought it was working, but now I'm not sure. I use my Gear S3 so often to pay, now I'm not sure LOL.

Update on the effort to revert back to CRK1.
Used the modified Odin, and un-checked auto-reboot. Phone remained in Download mode.
I could not figure out a way to go from Download mode to recovery mode directly. If someone knows how to do this, it would be appreciated if you could let me know.
However, rather than the "Error!" message, I received a "Erasing" message. Than the phone rebooted, and just kept rebooting, going from T-Mobile splash screen to Samsung and back over and over, with some optimizing apps screens thrown in for good measure.
So I tried again with auto-reboot on, and this time received the "Error!" message, and was able to go into recovery once that happened.
The odd thing is, nothing on my phone was changed, other than having to redo the Samsung biometrics for security. All of my apps and accounts and emails were already there, undeleted.

One more update on the S-Pay. After reinstalling the Update.zip from my SD card in Recovery, iIt does seem like there may have been a change. It is now doing the vibrate thing, which I don't think it was doing before. I will put it to the test later this week.

Downgrade Successful
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.

pzzamakr1999 said:
Performed Factory Reset from Phone menus. (not doing so kept resulting in an unauthorized factory reset prompt)
Performed Factory Reset from Recovery Menu.
Cleared Cache through Recovery Menu
Used Patched Odin
Kept Auto-Restart Checked
Used SamMobile CRK1
Phone restarted successfully.
Click to expand...
Click to collapse
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!

Mr. Orange 645 said:
Yes! I'm sorry I thought I told you to try a factory reset. You have to factory reset when downgrading. Otherwise bootloop city. Sorry I wasn't more clear, I could've saved you some frustration.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
I just went back and re-read my posts. I never said try a factroy reset first. Grrr...I'm so sorry!
Click to expand...
Click to collapse
No worries, and I did very much appreciate the help. I should have realized that that should come first. I was a bit frustrated and wasn't thinking logically. It was actually the "fixing apps" message you get when you upgrade that clued me in I wasn't properly resetting the phone prior to install.
Regardless, its all good, and now that I know how to do it, I'll be more inclined to try these out in the future.

Any specific reason for the downgrade? Anything not working?

Camera issues on pie beta
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue

Fitted2 said:
My ar emoji not working on this pie update and sometimes force closes any1 else having this issue
Click to expand...
Click to collapse
Yes

Mr. Orange 645 said:
Yes
Click to expand...
Click to collapse
You downgraded because no AR emoji? And what force closes are you having?

dami00976 said:
You downgraded because no AR emoji? And what force closes are you having?
Click to expand...
Click to collapse
I never said I downgraded.

Root [TWRP + Magisk] kills device Security :: Pin/Fingerprints broken

Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you

dekalbcountyman said:
Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you
Click to expand...
Click to collapse
did you encrypt your device? when you reboot, do you see an animation of a pad lock?

bober10113 said:
did you encrypt your device? when you reboot, do you see an animation of a pad lock?
Click to expand...
Click to collapse
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
Are you using Snapdragon or Exynos?

mmjs14 said:
Are you using Snapdragon or Exynos?
Click to expand...
Click to collapse
Sir, I am using a
Galaxy Note 9
SM-N960F Internationals Unlocked
Alpine White
Exynos
Boot loader is TWRP and OEM Unlock is staying open permanently
I have all the hardware required, just need to overcome this software quirk so I can lock my phone when I’m not using it

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
ive never seen this. what firmware are you on?
have you tried to download the very latest and completely wipe your phone? use samfirm tool 0.3.6 do dl the latest.
fill up all the slots with the md5 files u dled with samfirm and flash using odin( in csc slot use csc.md5 instead of home_csc.md5.)
go dl
magisk zip:
https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
and apk:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.2.0/MagiskManager-v7.2.0.apk
ketan oem fix +root
https://www.androidfilehost.com/?w=files&flid=281291
once back on latest stock firmware root again using twrp 3.2.x.x tar
flash it with odin but go to option and uncheck autoreboot
and flash twrp.tar in the AP slot.
once successful, manualy reboot phone to recovery( dont let it boot to homescreen! so hold vol up + Bixby +power
once in twrp swipe to get in recovery. go to wipe button and Format ( type yes) and go to reboot button and choose reboot to recovery
once back to recovery go again to wipe button and choose factory wipe.
once done flash dr ketan oem and root zip. ( within the aroma setup of that zip choose yes to both option for root and kernel)
once finished you can now flash the latest magisk.zip as dled earlier.
now reboot and setup your device. once done you can install magisk manger .apk that was dled earlier.

Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate

dekalbcountyman said:
Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate
Click to expand...
Click to collapse
actualy the root method that dr ketan created is just a way to bypass an issue that not all phones have(rmm state aka binaries error when booting.
but technically the method should be;
flash twrp, format, reboot again to recovery and flash official magisk .zip
you can also rely on rom developpers to flash their version instead of stock android via odin. this allows you to not always have to go through the twrp/root procedure each time and also rom devs include nice additional features.
anyways glad i could help.

Urgent help regarding downgrading from pie to oreo or nougat....

Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.

drvish said:
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
Click to expand...
Click to collapse
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.

Only if they are same bootloader
Sent from SM-N950U Still Rooted Note 8

stonedpsycho said:
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Click to expand...
Click to collapse
Oh.... i checked my bootloader version is 6. Is there any way to downgrade to version 5 ????

No, there is not, sorry

Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that

drvish said:
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
Click to expand...
Click to collapse
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/

stonedpsycho said:
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
Click to expand...
Click to collapse
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app

drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
As far as I am aware it is not possible without root.

drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
Just use Magisk Hide to disguise, that you are using root

Reaper1337 said:
Just use Magisk Hide to disguise, that you are using root
Click to expand...
Click to collapse
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....

drvish said:
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
Click to expand...
Click to collapse
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.

Xenos7 said:
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Click to expand...
Click to collapse
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.

I hope someone can provide me edited s health apk

drvish said:
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
Click to expand...
Click to collapse
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8

Xenos7 said:
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Click to expand...
Click to collapse
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....

drvish said:
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
Click to expand...
Click to collapse
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.

Xenos7 said:
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Click to expand...
Click to collapse
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily

drvish said:
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
Click to expand...
Click to collapse
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.

Xenos7 said:
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Click to expand...
Click to collapse
Hmmm.... lets wait for some godman to do the favour..... i am from medical profession so dont know much abt this coding stuff. Otherwise i would have done that myself :laugh:

Fixing bootloop?

so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.

mistermojorizin said:
so my bramble spazzed and did a soft reboot and then the system ui wouldn't load (I was able to use the phone, but not the status bar, navbar). i disabled the lockscreen security and removed my magisk modules. then i tried flashing the stock firmware (december) *after erasing the -w*, then i tried sideloading the december ota via recovery, then i tried to do the same withe november versions and then again the december, you get the idea. nothing doing, the best i get is it'll get to "pixel is loading" for a split second then go to bootloader. anyone have any suggestions for me?
sorry, asking on the P5 forum because the phones are so similar the P5 forum is more active.
Click to expand...
Click to collapse
Are you booting on the right slot ?

jaythenut said:
Are you booting on the right slot ?
Click to expand...
Click to collapse
Thanks, yes I was. I ended up dirty flashing the stock firmware from December and from November and sideloading otas from both months over and over till it was working again. Took all day but I saved my data. I was flashing the all carrier December image as they was the one I was on, not flashing verizon one did the trick. Something to keep in mind for next time.