Related
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
A lot of users are saying they got an update with August security patches and other improvements.
But now it's almost the end of August and I haven't have got any update after the July update.
Build number: LLD-AL10 8.0.0.170(C675)
Varient:Indian
Any help?
1.) Is your boot-loader unlocked ?
2.) Do you have a Custom Kernel or Recovery Installed?
3.) Are you Rooted?
If the answer is yes to any of them then thats why your not getting any OTA's, If Yes is on 1.) then simply issue the fastboot command to relock the device "fastboot oem relock <bootloader-code>" If its yes to 2.) / 3.) Then your going to need to flash the phone back to stock before then relocking the bootloader.
hacktrix2006 said:
1.) Is your boot-loader unlocked ?
2.) Do you have a Custom Kernel or Recovery Installed?
3.) Are you Rooted?
If the answer is yes to any of them then thats why your not getting any OTA's, If Yes is on 1.) then simply issue the fastboot command to relock the device "fastboot oem relock <bootloader-code>" If its yes to 2.) / 3.) Then your going to need to flash the phone back to stock before then relocking the bootloader.
Click to expand...
Click to collapse
1) Was unlocked
2)Had TWRP
3)Was rooted
I switched back to stock because of constant bugs especially the camera(what's the use of keeping a camera oriented phone in the pocket if it's camera is of no use?)
I'd used HuRupdater to flash the firmware. Now bootloader's relocked and everything's working fine except updates.
I think I flashed the wrong firmware maybe ( I forgot the build number so had to guess. I was sure I had an LLD-AL10 and that there was a C675 and 8.0 in the build number. I matched the changelog with that of the last update I got and then I kinda found out that everything matched to LLD-AL10 8.0.0.170(C675) )
Would one stop getting updates if they installed wrong firmware?
Everything works fine except updates.( And the bootloader 'relocked' status in fastboot).
Should I just flash the August update with HuRupdater( that's gonna be a lot of hassle as I have to unlock bootloader and do all those stuff) or can I update via any other method?
Right you can use Firmware finder on your phone which is a good start.
So using FF select then next version up from your current and only select a OTA-MF, then make sure its for your phone by clicking check firmware access.
If its for your phone then simply use the in-app proxie and connect to a wifi point. Once you have done this edit that Wifi via Settings and change the Proxie to Localhost port 8080. Then go the System and Update.
Now it should download the small version OTA to your phone and reboot to try to install it, it it goes thought and installs without error then great, if it errors out when you boot back into android it will offer the Full OTA without using FF to which will then flash proper without losing data then see if OTA's work after that.
hacktrix2006 said:
Right you can use Firmware finder on your phone which is a good start.
So using FF select then next version up from your current and only select a OTA-MF, then make sure its for your phone by clicking check firmware access.
If its for your phone then simply use the in-app proxie and connect to a wifi point. Once you have done this edit that Wifi via Settings and change the Proxie to Localhost port 8080. Then go the System and Update.
Now it should download the small version OTA to your phone and reboot to try to install it, it it goes thought and installs without error then great, if it errors out when you boot back into android it will offer the Full OTA without using FF to which will then flash proper without losing data then see if OTA's work after that.
Click to expand...
Click to collapse
I checked and this is what happened.
FF detected my phone as LLD-AL10C675
The latest update that's is approved is
LLD-AL10 8.0.0.181(C675CUSTC675D1)
It is B181
But that update is from June. So I searched for LLD-AL10 and pressed ok , so that it shows all firmwares for lld al10.
And I think I found the one I have currently installed(build number and changelog matches) LLD-AL10 8.0.0.170(C675CUSTC675D1). It is from 11/7/2018. Everything above says either firmware not approved or has a wierd term cn in the available models section.
This is something I quite don't understand. When I check firmware access it says lld-al10:all-cn.
I think cn stands for China.( Uploading screenshot)
Would it be safe for me to install the update?
Also is it necessary to download the update just above the one I have installed now or can I skip to the latest one?
Sorry if that's a lot of questions.
I'm in a tight corner now.
I can't get any updates using the dns method or the in app proxy method.
This sucks as I was able to get an update using the dns method 3 weeks back. I didn't install it. I checked for updates, it showed updates, then I stopped dns and things went back to how it was(no updates ?). Today I tried again and nothing happened.
Crazy phone?
Are you selecting the smaller updates as it will not work with full ota's any more.
Sent from my LLD-L31 using Tapatalk
hacktrix2006 said:
Are you selecting the smaller updates as it will not work with full ota's any more.
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
I tried it with both the small one and full ota update
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Yup I'm sure I did those right. I tried both the VPN and proxy methods. As I told VPN used to work.
Anyways I'm gonna wait and try it a few more times. Then I might use HuRupdater.
Thanks for your replies man ?
hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
OMFG bro I fixed it.
You see Huawei had rolled out an update for the 'system update' app through playstore. I had updated it. And after I uninstalled the update for it, things are starting to work again ?.
Only 3 questions remains.
1) Can I install firmware that is not approved?
2)Is it necessary to install the update just above the version I
have currently installed?
3)Is it okay if FF says it's approved but has the part LLD-AL10-
all-cn:all ?
Does the cn part matter ?
Would be very grateful if you could help
1) Yes
2) No
3) CN= China. Personally I wouldn't, plus I don't speak Chinese , why would you want to ? I also like having full access to Google playstore.
On an aside, I'm beginning to get the impression you won't be happy till you really brick your phone . :laugh::laugh:
hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
Sparkrite said:
1) Yes
2) No
3) CN= China. Personally I wouldn't, plus I don't speak Chinese , why would you want to ? I also like having full access to Google playstore.
On an aside, I'm beginning to get the impression you won't be happy till you really brick your phone . :laugh::laugh:
Click to expand...
Click to collapse
?That's kinda my thing (I desperately break stuff then fix them)?
Thans ?
hacktrix2006 said:
Well it worked for me from going from LLD-L31c432b133 to LLD-L31c432b136 as the small OTA came down failed to install so then it downloaded the full version are you sure your setting the WiFi to use the proxies using localhost and port 8080?
Sent from my LLD-L31 using Tapatalk
Click to expand...
Click to collapse
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
I used the FF app on mobile then used in app proxie connected to a wifi point and edited the connection to enable proxie on localhost port 8080. I also only downloaded only the small OTA, however it will fail to install then once you rebooted back into android go system update and then press the 3 dots and go for Full Download that will fix it.
Just a point you may have the same Firmware even the same model but they are not made equal.
Also check Google play store app for Huawei System Update it should look like the picture that's attached then click uninstall and reinstall install the app too before starting as reinstalling that app can help alot.
hacktrix2006 said:
I used the FF app on mobile then used in app proxie connected to a wifi point and edited the connection to enable proxie on localhost port 8080. I also only downloaded only the small OTA, however it will fail to install then once you rebooted back into android go system update and then press the 3 dots and go for Full Download that will fix it.
Just a point you may have the same Firmware even the same model but they are not made equal.
Also check Google play store app for Huawei System Update it should look like the picture that's attached then click uninstall and reinstall install the app too before starting as reinstalling that app can help alot.
Click to expand...
Click to collapse
Many thanks for your prompt reply.
So Ive already done all this because it may be related but no luck.Last time I used FF was to get the B133 which already didnt work on the 7th August,I then uninstalled the FF app,stopped the proxy localhost etc. and right after that I did the update check through system update and the B133 FULL was offered to download,so the B133 was made properly through system update right after all the procedure with the FF.
rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
Try uninstalling the update for the system update app then use the VPN or proxy method.
Maybe the update just hasn't reached you like me.
Fredin_ said:
Try uninstalling the update for the system update app then use the VPN or proxy method.
Maybe the update just hasn't reached you like me.
Click to expand...
Click to collapse
"Maybe the update just hasn't reached you like me"...I will keep that and just have patience. Ive tried everything but there is no update yet....
Many thanks once again for your reply
rostropol said:
I have tried this procedure more than three times and it just doesn't work. I have the same model version C432 and the same firmware B133. I even downloaded the full Ota file and tried through SD card update ("#" #2846579#"#"), still nothing. When I connect it to Hisuite it says that I have the last official version. Any suggestions?
Click to expand...
Click to collapse
rostropol said:
"Maybe the update just hasn't reached you like me"...I will keep that and just have patience. Ive tried everything but there is no update yet....
Many thanks once again for your reply
Click to expand...
Click to collapse
?.
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
Does doing that wipe my device? Or do I get to keep my stuff?
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Nachorl250 said:
Does doing that wipe my device? Or do I get to keep my stuff?
Click to expand...
Click to collapse
Nope, its a regular update so no need to wipe anything
Already try my apps and games (fortnite, arena of valor) and they work perfect!
Ed Murray said:
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Click to expand...
Click to collapse
Tried everything, to be honest I was just sure that the Samsung+ app would check where you are in the world and if your not on the US it will simply not let you join the beta, the method above worked flawlessly for me!, I'm running One UI at the moment with the dark theme and its awesome!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
BigMosely said:
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
Click to expand...
Click to collapse
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
sFranKv said:
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
Click to expand...
Click to collapse
Can you flash the unlocked firmware without loosing data?
BigMosely said:
Can you flash the unlocked firmware without loosing data?
Click to expand...
Click to collapse
Yes, I did. No data loss.
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
papashex said:
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Click to expand...
Click to collapse
Yea themes are not on beta for some reason, good it worked for you!
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
I would not know, I guess we need to wait until beta 2 update and see, probably won't be getting it and we will need to download the new OTA and flash again on recovery
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
Ok. First of all. Green and gold till I'm dead and cold.
Second of all, if you flash the U1 firmware and sign up for the beta, then you'll get OTAs automatically through settings.
If you flash the U1 firmware and can't get into the beta program, you can download the update.zip from firmware.science. You will have the official beta build, but you won't get updates through settings, because you aren't part of the beta program.
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
GBPackerFanForLife said:
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
Click to expand...
Click to collapse
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Mr. Orange 645 said:
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Click to expand...
Click to collapse
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
GBPackerFanForLife said:
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
Click to expand...
Click to collapse
Yes. That's why I said use the modified version.
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
GBPackerFanForLife said:
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
Click to expand...
Click to collapse
Yes, you are not part of the official beta.
As far as speaker loudness I have no idea.
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.
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: