No software updates after ADB - Samsung Galaxy S10 Questions & Answers

Hey, I own a Galaxy S10+ and I've noticed I get no updates at all. It keeps saying "Current software up to date" and sometimes "DM Initialization is not ready" or something. My sister owns the same phone on the same network and she gets updates. I've noticed it started happening after doing something related to ADB. I was trying to install Navigation Gestures and had to install ADB. After that, issues started arising. Any ideas?

Altair_47 said:
Hey, I own a Galaxy S10+ and I've noticed I get no updates at all. It keeps saying "Current software up to date" and sometimes "DM Initialization is not ready" or something. My sister owns the same phone on the same network and she gets updates. I've noticed it started happening after doing something related to ADB. I was trying to install Navigation Gestures and had to install ADB. After that, issues started arising. Any ideas?
Click to expand...
Click to collapse
Which build is on your phone?

charkatak said:
which build is on your phone?
Click to expand...
Click to collapse
ppr1.180610.011.g975usqu1asba

From what I have seen if you manually update via a download from firmware science you usually just keep looking there for updated firmware then you can manually update in recovery through sd card.That's what I've been doing for the past 3 to 4 updates.

Altair_47 said:
ppr1.180610.011.g975usqu1asba
Click to expand...
Click to collapse
If your phone is unlocked US model, then the latest version is: G975U1UES1ASDB
1) You can try removing sim card, restart your device and then check for update...
OR
1) You can back up your phone using Samsung's backup option, then do factory reset to see what went wrong. After that restore from that backup

Charkatak said:
If your phone is unlocked US model, then the latest version is: G975U1UES1ASDB
1) You can try removing sim card, restart your device and then check for update...
OR
1) You can back up your phone using Samsung's backup option, then do factory reset to see what went wrong. After that restore from that backup
Click to expand...
Click to collapse
Resetting my phone did not work. Removing the sim did not work either.

Go to firmware science find your model s10 click on your current firmware it will show you the next firmware jump from asba,download and save to sd card,power your phone to recovery mode and flash update via sd card and repeat steps to catch up to current firmware.
---------- Post added at 05:35 PM ---------- Previous post was at 05:29 PM ----------
Or jump down a section to galaxy s10 guides and look for the thread At&t OTA and non OTA updates G975U and you will have all the links you need to catch up to current firmware.

Related

Repeat update notification

Afternoon all, just wondering if anyone could help on a quick problem - my Nexus 6 keeps prompting me to update but when I do it hangs after the reboot with what I assume is the recovery error message (red exclamation mark). I'm already on build LMY48I on 5.1.1, which I was under the impression was the September 2015 security patch. I'm fully stock, not rooted or any other mods. I am abroad currently, which I wouldn't imagine has any effect?
Could anyone offer any help on this or steer me in the right direction for further information.
Thanks in advance.
Latest build is LMY48M. OTA may fail because of corrupted download.
You may wanna update your signature.
Yeah, OK, thanks, not been around these parts for awhile.
Would you mind letting me know how I would go about getting a fresh download of the update using OTA?
Thank for the reply.
Still booting normally? Bootloader locked?
When you get to error with Android logo with tummy open press Power then VolumeUp this will show more details about the error. Write everything down.
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
gardy09 said:
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
Click to expand...
Click to collapse
If you're overseas you may be getting an incorrect build, not quite sure how that works
Strangely I thought it might have something towards do with being in Spain. I'll factory reset when I get home and see if that works.
Me too
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
simms22 said:
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
Click to expand...
Click to collapse
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
soccerguy243 said:
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
Click to expand...
Click to collapse
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Didgeridoohan said:
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Click to expand...
Click to collapse
I have 47Z installed. I'll use nexus root toolkit to get the latest. Thanks SO MUCH!
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
gardy09 said:
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
Click to expand...
Click to collapse
Have you ever found out more details about update error? Press Power then Volume Up on error screen.
Will do it now, hang on...
This is the error message I get...
gardy09 said:
This is the error message I get...
Click to expand...
Click to collapse
At this point you have few choices.
File bug report and wait for resolution.
Try Factory Reset. Using PC try fastboot format userdata and format cache.
Unlock bootloader and flash factory image. Might just well go straight to 6.0 MRA58K. You will loose all your private data either way. Backup all your private stuff.
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
Here is guide how to flash factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
You'll have to find the update from ur current version to the new version. You'll probably have to get LMY48M, didn't see one from I
Sent from my Nexus 6 using Tapatalk

Oreo OTAs

Close thread
Should I bother trying this? What's new? I'm on U firmware which I like but should I wipe to go to Oreo?
Anybody tried this?
vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse
Personally I think is not worth it. This is not final build and will delete data from your device. Then next one will show up in couple days or even (maybe) tomorrow. If I will you I will wait for around another 3-4 weeks to get more stable build.
Sent from my SM-N950U using XDA Premium HD app
I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
vineet381 said:
Anybody tried this?
Click to expand...
Click to collapse
DO you know can i install this update on my 935U model and how can i do it ?
You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Janitor87 said:
DO you know can i install this update on my 935U model and how can i do it ?
Click to expand...
Click to collapse
Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
nivron said:
You need to ODIN to 935A's latest build (BRA1) then you can upgrade to this Oreo build by flashing it in Recovery.
Click to expand...
Click to collapse
BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Janitor87 said:
Can you please provide me with the link on this Odin file because I can not find any working link. NOw i'm using BKQH1
Click to expand...
Click to collapse
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
nivron said:
BRA1 ODIN Files
Thanks to @norbarb for that link. I downloaded it the other day. You will have to unRAR the files after you open the initial ZIP file -- otherwise ODIN won't find the files.
Click to expand...
Click to collapse
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
Without a PC, you cannot update to Oreo unless you're already on the AT&T G935A firmware.
Sent from my SM-G955U using Tapatalk
As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
Janitor87 said:
I don't have a windows PC at the moment. Can you plz provide me with a OTA update files. I updated G935AUCS4BQH1-to-S4BQJ2
HOw much updates i should update to the G935AUCS4BRA1
Thank you.
Click to expand...
Click to collapse
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQJ2-to-U4BQK2-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCU4BQK2-to-S4BQL1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BQL1-to-S4BRA1-UP
https://samsung.firmware.science/download?url=48775/1488/SS-G935AUCS4BRA1-to-U4CRB5-UP
In that order
Sent from my SM-G955U using Tapatalk
You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
nivron said:
As far as I can tell, there's not an OTA sideload update path to BRA1. Someone else may be able to chime in with it.
I assume you are not an AT&T customer, otherwise you could use the official OTA method to get to BRA1.
Click to expand...
Click to collapse
Janitor87 said:
You are right. I'm using the Verizon 935V model anbd now I flashed ATT firmware and wanna try to install OREO update
Click to expand...
Click to collapse
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk
I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
FatalONEM8 said:
You're in luck then, I've laid out all the OTAs you need to install to your device.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
---------- Post added at 20:02 ---------- Previous post was at 19:49 ----------
I found my issue I forgot to enable USB debugging mode. It has fixed my issue.
-------------------------------
Janitor87 said:
I'm trying to update now.... I will inform if I will be a lucky man and successfully update my phone
---------- Post added at 19:49 ---------- Previous post was at 19:12 ----------
[email protected]:/home/alex/Downloads# adb sideload update.zip
serving: 'update.zip' (~31%) * failed to read command: Success
I can not update
Click to expand...
Click to collapse
nivron said:
I tried it -- the installation took about an hour in Recovery, mainly stayed in the "Patching system files". This install *WILL* wipe your phone (not your SD card though).
The build was super fast (even faster than a fresh Nougat flash).
There were two things that caused me to flash back to Nougat.
- The Wi-Fi was extremely weak. At my desk at work, I can normally see 6 Wi-Fi networks. 4 of them are in my office. With Oreo, I could only see two of them, and it struggled to stay connected to the one that I normally have full signal on.
- Also, my AT&T Gear S2 Classic could not be connected. Upon attempting to pair (after confirming the PIN on phone/watch) Samsung Gear gave a message stating that I need to ensure my phone was compatible and that I had the latest Samsung Gear app. I confirmed that there were no available updates for ANYTHING in the Play Store and Galaxy Apps. Both stores showed that my app was up to date.
If it weren't for those two issues, I'd still be on the Oreo build right now.
Another point -- I experienced my first freeze/reboot on this phone in Oreo. I've had the phone since June of last year and never had any freeze/reboot issues previously. Never dropped or gotten the phone wet, etc.
Hope this helps anyone who is wanting to flash the build!
Click to expand...
Click to collapse
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse
vineet381 said:
Thanks for the feeback, I tried this and I agree on weak Wifi on Oreo. I will keep and play with it for sometime before going back to Nougat. Hopefully new stable version shows up soon.
Click to expand...
Click to collapse
I face the same issues you have described. Originally after applying the Oreo update, I was not able to enable Bluetooth nor WiFi. I had to reboot to recovery and wipe cache.
Once that was done, I was able to get WiFi and Bluetooth to work.
I have the Galaxy Fit2 and was not able to sync watch to the phone with the same error you received. ( I tried the version 3..1.80.80109 of Samsung Accessory Service as suggested in another thread, no luck.)
WiFi as you described is pitiful, luckily I don't rely on WiFi as much so I will continue on with this Oreo build.
Does anyone know how to turn off the red heart rate sensor light off? It is accidentally turning on even if I dont get my finger on it after oreo update
---------- Post added at 02:19 PM ---------- Previous post was at 02:08 PM ----------
Janitor87 said:
You are a lucky man because i'm flashing via adb and only 59 %. Which issue with a WiFi ? Can you please provide me more information and maybe do you know who will it fix ?
Thank you
Click to expand...
Click to collapse
Wifi issue meaning weak signals in Wifi connection on Oreo. I simply followed the steps in flashing through SD card and it took a while (40 mins or so) but eventually it went through the install.

How to get the Beta "Update" on your Note 9 U1.

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.

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.

Question System Update Issue (Fixed)

Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Update: I attempted the system update again and left it overnight. This morning it's still stuck on the same installing screen.
Can someone share the Android Version screen of an unlocked Pixel 7. I think I might be updated and the update is just a bug?
Update: I determined I had an OTA update failure. So I just adb sideloaded the OTA file and it's fixed now.
KillerDroid96 said:
Last night I did the system update and left it overnight. This morning the update wasn't installed and asked me to update again. So I started it again 3 hours ago and it's still not done. Anyone else's update taking this long?
Click to expand...
Click to collapse
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
ern88 said:
I saw your previous post about wifi not staying on. So if that happening while dl. It my screw it. Because it's jumping back to network data and the setting maybe set to only update over wifi.
Click to expand...
Click to collapse
It's set to mobile data and that should only impact the downloading not installing. 4 hours now and still stuck. I'm considering rebooting at this point.
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Giovanni9518 said:
I had the same problem, i rebooted and it all seems gone. But I checked the factory images and everything is up to date.
Click to expand...
Click to collapse
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
KillerDroid96 said:
That didn't work. I'm back at the same screen as before after hitting restart now. I also noticed that Google play system update is on July.
Click to expand...
Click to collapse
My Google play system also states that too.
Well I give up. I restarted and I'm just not going to update for the time being.
ern88 said:
My Google play system also states that too.
Click to expand...
Click to collapse
I think I'm actually fully updated and its just a bug?
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
KillerDroid96 said:
@ern88 can you share a screenshot of your Android Version screen please. I'm trying to determine if I'm fully updated and its just a bug.
Click to expand...
Click to collapse
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
ern88 said:
Here is the ver I'm on. I see you still are on the factory version. Not the Oct update. By chance. Did your carrier give you a new sim card with your phone? Telus have me a new sim card when I bought the phone.
Click to expand...
Click to collapse
Thanks! I determined I had an OTA
update failure. So I just adb sideloaded the OTA file and it's fixed now.
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
gorilla p said:
So I'm having the same issue, but potentially for a different reason.
I'm rooted. Typically to resolve this issue, you
1 - select Uninstall Magisk/Restore Image. This restores your stock boot image
2 - Install OTA update
3 - You then install Magisk again once the update completes and select "flash to inactive slot" prior to reboot.
The Uninstall/image restore in Magisk is not removing Magisk and the update still fails.
I'm wondering if it is restoring the boot.img, when it is the initboot.img that has been modified.
I could be wrong, just thought I'd note my issue.
Click to expand...
Click to collapse
They've covered this in the two big threads regarding unlocking / rooting in the 7 Pro-forum.

Categories

Resources