Hello everyone,
I am looking for some advice on what started as a question about a firmware update problem, but has now become a more general question on recommended course(s) of action for a handful or problems. I’ve tried to be as detailed as possible, since I don’t know exactly what is relevant. That said, for the sake of “manageability”, I first included a brief overview, followed by my questions, before adding the details. Any help, suggestions, or advice will be greatly appreciated. Thanks!
-Leonardo
Phone information:
Galaxy S7 (SM-G930P) (Sprint) (not rooted)
Android 7.0
Software version: G930PVPS5BRA1
Android security patch level: January 1, 2018
Summary
A couple weeks ago, I downloaded and attempted to install the latest update (G930PVPU6BRD2); however, the installation failed numerous times (always at around the 27% mark). I’ve tried numerous troubleshooting attempts (found here on XDA, on Google, and suggested to me by Sprint), but nothing worked. I also checked sammobile for the latest update, but it is not listed.
Originally, I was going to ask for help with this issue; however, my phone has been having other problems – random reboots, sporadic slowdowns, strange sounds while I’m making calls (I’m not crazy, I promise).
Questions
-Is it possible that these problems are caused by some kind of malware/spyware? If so, what is the best way to check? I’ve scanned my phone with both Malwarebytes and Kaspersky; neither one turned up anything.
-Is there else anything I can/should do to verify the phone’s integrity?
-Any ideas as to what might be the problem(s)?
-Is there a “nuclear” option that might resolve all of these problems? If so, would it be appropriate in this case, or is that overkill?
Details
Regarding the firmware update, I can successfully download the file, but the installation fails at around the 27% mark every time. I’ve implemented numerous troubleshooting suggestions, including (1) updating with the phone at least 80% charged, (2) updating with the phone at least 80% charged and plugged in, (3) wiping the cache partition, (4) downloading the update via mobile web, or on a different WiFi network, (5) booting in Safe Mode before downloading and attempting to install, (6) trying to update via Samsung SmartSwitch, (6) killing all running apps prior to downloading and attempting to install, (7) making sure I have at least 3 GB of storage space (I do). None of these worked.
As I mentioned, there are a few other problems, including (1) the phone randomly freezes and reboots, (2) the phone sometimes lags for a few seconds, then returns to normal; (3) when I’m making calls, the phone makes intermittent beeping noises – sometimes the noises sound like the person on the other end is dialing while on the line (I always ask, and they say they are not), and other times it’s a loud, more sustained beep (similar to when a truck is reversing). I’ve tried to identify a pattern to these noises (e.g. if they happen at specific intervals, or when I’m talking to specific people, or when I’m connected to certain networks, or using speaker/headphone/Bluetooth), but there does not seem to be any.
These problems initially started in June 2017. A few months after they started, I did a factory reset on my phone as an attempted fix. However, the problems have all returned. That said, before the reset, I used Samsung’s SmartSwitch to back up my personal files, which I then restored to the phone. I don’t know anything about Android malware, but it has just occurred to me that, if that’s the problem, then the factory reset may not have worked because I may have inadvertently transferred the problem(s) back to my phone.
I don’t have any games installed on my phone, and the apps that I do have are few in number, are denied permissions that are not relevant to their functions, and are all from the Play Store (not foolproof, I know). I’ve removed (or disable, when not removeable) all the apps that came preloaded on my phone (courtesy of Sprint). Finally, for what it’s worth, I have Malwarebytes for security (scans do not turn up any problems), I use Prey Panel for tracking, and Lockwatch for added security. I’ve had these three since before the problems started, so I don’t know that they could be to blame. I also installed Kaspersky for a while (it also did not identify any problems), but have since removed it.
Sounds possible the app / data restore is causing the problems, only way to know would be reset again, and install everything direct from the play store instead of restoring backups
As for upgrading, you could download the firmware on a PC using samfirm tool here on XDA, or from updato.com / sammobile.com, then update using ODIN 3.12.7
Instructions for ODIN flashing are bottom of the firmware download page on sammobiles site, and posted dozens of times in these S7 forums
samfirm tool is the fastest way to get the latest firmware, other two options are painfully slow
Only tips you need to know are:
CSC = Factory reset after the flash
HOME_CSC = No reset
Pick only one to add to ODIN along with the other 3 parts of the firmware, flash all 4 together
*Detection* said:
Sounds possible the app / data restore is causing the problems, only way to know would be reset again, and install everything direct from the play store instead of restoring backups
As for upgrading, you could download the firmware on a PC using samfirm tool here on XDA, or from updato.com / sammobile.com, then update using ODIN 3.12.7
Instructions for ODIN flashing are bottom of the firmware download page on sammobiles site, and posted dozens of times in these S7 forums
samfirm tool is the fastest way to get the latest firmware, other two options are painfully slow
Only tips you need to know are:
CSC = Factory reset after the flash
HOME_CSC = No reset
Pick only one to add to ODIN along with the other 3 parts of the firmware, flash all 4 together
Click to expand...
Click to collapse
Thank you for your response. In your experience, do you recommend one over the other? That is, should I reset and install direct from the Play store (and then maybe even try the OTA update again), or just run the factory reset option (CSC) from the get-go?
Also, in reference to your first point: if that's the case, would it be just the apps that are affected? In other words, if I reinstall apps directly from the Play store, but restore, for example, SMS messages, do you think that would be okay?
Leonardo2 said:
Thank you for your response. In your experience, do you recommend one over the other? That is, should I reset and install direct from the Play store (and then maybe even try the OTA update again), or just run the factory reset option (CSC) from the get-go?
Also, in reference to your first point: if that's the case, would it be just the apps that are affected? In other words, if I reinstall apps directly from the Play store, but restore, for example, SMS messages, do you think that would be okay?
Click to expand...
Click to collapse
If you are going to reset the phone anyway, and because of the bugs, I'd recommend using CSC, no need for OTA that way for now either as you will be flashing the latest firmware to begin with
And to troubleshoot, I would not restore anything just yet, flash the phone and allow the reset, set it all back up using official play store only, see how things are for a day or so, then if all is well begin restoring your backup, SMS should be fine, apps can cause problems, system apps definitely can so I would hold off from them, and if you are restoring a backup from an older version of Android then you are even more likely to run into issues with compatibility
So in a nutshell I'd do this:
Flash stock with ODIN using CSC
Install only from Play store for 1 day~
Restore only SMS
Then it is entirely up to you if you want to risk restoring anything further, but at least this way you will know the problem if all was fine, you restore and it goes wrong again
Good luck
*Detection* said:
If you are going to reset the phone anyway, and because of the bugs, I'd recommend using CSC, no need for OTA that way for now either as you will be flashing the latest firmware to begin with
And to troubleshoot, I would not restore anything just yet, flash the phone and allow the reset, set it all back up using official play store only, see how things are for a day or so, then if all is well begin restoring your backup, SMS should be fine, apps can cause problems, system apps definitely can so I would hold off from them, and if you are restoring a backup from an older version of Android then you are even more likely to run into issues with compatibility
So in a nutshell I'd do this:
Flash stock with ODIN using CSC
Install only from Play store for 1 day~
Restore only SMS
Then it is entirely up to you if you want to risk restoring anything further, but at least this way you will know the problem if all was fine, you restore and it goes wrong again
Good luck
Click to expand...
Click to collapse
Thank you for your CSC tip -- that was really helpful.
I checked the sources you provided, but I couldn't find version G930PVPU6BRD2 anywhere; they all have the January (G930PVPS5BRA1) version. Based on this XDA post, it seems others are having this same problem.
I went ahead through all of the steps you suggested anyway, except with the previous firmware version. Once the phone was up and running, it asked me to install the update. I tried, and it failed again (at 27%, just as before). I contacted Sprint and was told they "don't see a known issue with this update", so I'm not sure what the problem is. There were a few places on Google that claimed to have the latest firmware, but it seems risky to download from unknown sources that are not recommended anywhere.
Any other ideas?
Leonardo2 said:
Thank you for your CSC tip -- that was really helpful.
I checked the sources you provided, but I couldn't find version G930PVPU6BRD2 anywhere; they all have the January (G930PVPS5BRA1) version. Based on this XDA post, it seems others are having this same problem.
I went ahead through all of the steps you suggested anyway, except with the previous firmware version. Once the phone was up and running, it asked me to install the update. I tried, and it failed again (at 27%, just as before). I contacted Sprint and was told they "don't see a known issue with this update", so I'm not sure what the problem is. There were a few places on Google that claimed to have the latest firmware, but it seems risky to download from unknown sources that are not recommended anywhere.
Any other ideas?
Click to expand...
Click to collapse
Looks like that newer firmware is OTA only right now, usually takes a few days to go from OTA to downloadable full firmware
I would just flash back to the January firmware and hold off on the update for now, I see some people mentioning bootloader versions causing the problem and from what I see in the January firmware, Sprint have reached Version 5 already G930PVPS5BRA1, and the new update is moving up again to version 6 G930PVPU6BRD2
The G930F running Oreo is still only on version 2
So yea, flash back to the working latest available, then do not update, see whether it hits Samsung servers as a full firmware, or if Sprint finally see the problem and remove it
If you are forced to update during setup which you might well be, do not connect to wifi during setup (remove your Google account from Settings > Accounts before resetting / flashing to avoid FRP lock which will require a connection to unlock the device during setup
1.) Remove your Google account
2.) Flash Jan update using CSC to reset
3.) Skip WiFi connection during setup
4.) Disable Auto update once booted from update settings
5.) Connect to WiFi once booted to homescreen and ignore prompts to update if they appear
Related
I was lucky enough to get one of the earlier batches (pre import ban) of the AT&T HTC One XLs and I have enjoyed having it over the past 5-6 weeks. A few weeks back I decided to root my phone and unlock it as I wasn't having any luck upgrading via the OTA update. I believe that soon afterwards I started having a problem installing some larger files and updates, getting a "Package file is invalid" message via Google Play.
At first this only seemed to happen occasionally but a few days back, it started occurring with practically any update or install. I tried cleaning the dalvik and other caches, factory reset, and wiped the SD card without any improvement. Yesterday I decided to make the leap and install CleanROM, both out of curiosity and a hope to resolve my problem. I wiped the system via the recovery bootloader, wiped the cache, wiped the dalvik cache, and wiped the SD card and installed CleanROM. While the install went well and CleanROM is running perfectly, I still get the package invalid method with any install larger than 1mb or so. I am frustrated about this problem as I have enjoyed this phone up to this point. If anyone have any suggestions to resolve this repeated error I would be very grateful. Thanks.
I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
also check theses things. http://www.thespicygadgematics.com/2011/12/fix-android-package-file-is-invalid.html
Follow-up on suggestion
android addicts said:
I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
Click to expand...
Click to collapse
Thanks for the suggestion but it turns out exactly the opposite is true. I have been trying to install programs over wifi and they keep failing with the invalid package file message. After reading your suggestion, I turned off the wifi and tried installing several larger programs via the mobile network - they all downloaded and installed without a hitch! Crazy.
So, it looks like my problem might have something more to do with either my wifi network/router or with some aspect of the wifi hardware or software on my phone. Tomorrow I am going to try accessing and installing files from a different network and will post my results then.
So I have an old Galaxy S3 that I was playing around with, trying to figure out some basics to rooting, as I've never done it before. (I now have a new Galaxy S5 that I'd like to eventually root, but I figured if I was going to brick anything, it would be this older S3).
It has the stock Android 4.4.2 image on it.
After reviewing a number of forum posts on XDA and elsewhere, I've learned that this has a locked bootloader that hasn't been cracked. So, I decided to first try the easy route, and installed Towel Root.
After successfully rooting the phone, I uninstalled some apps that I probably should not have uninstalled, because now when I go to do a factory reset, the setup wizard allows me to select my language (English), but then fails with "Unfortunately setup wizard has stopped."
When I hit OK, I do get dumped out into the home screen, and the phone seems like its mostly (if not fully) functional, minus the apps that I removed which I shouldn't have removed.
So... is there any way of fixing this?
Bump
Moogly507 said:
So I have an old Galaxy S3 that I was playing around with, trying to figure out some basics to rooting, as I've never done it before. (I now have a new Galaxy S5 that I'd like to eventually root, but I figured if I was going to brick anything, it would be this older S3).
It has the stock Android 4.4.2 image on it.
After reviewing a number of forum posts on XDA and elsewhere, I've learned that this has a locked bootloader that hasn't been cracked. So, I decided to first try the easy route, and installed Towel Root.
After successfully rooting the phone, I uninstalled some apps that I probably should not have uninstalled, because now when I go to do a factory reset, the setup wizard allows me to select my language (English), but then fails with "Unfortunately setup wizard has stopped."
When I hit OK, I do get dumped out into the home screen, and the phone seems like its mostly (if not fully) functional, minus the apps that I removed which I shouldn't have removed.
So... is there any way of fixing this?
Click to expand...
Click to collapse
I'd suggest re flashing the 4.4.2 NE1 firmware. That should solve your problem. I'd suggest using Odin
Sent from my Nexus 5
Thanks.
I downloaded 4.4.2 from 2 different sources, and the md5sum were different for each, so I knew that at least 1 of them was either the wrong firmware or corrupted in some way.
After further research, I realized I could download Kies 3 onto my Windows computer (official Samsung software), and run a factory reset / image upgrade directly from the computer. I decided that was the safest method.
And it worked!
My Advanced Calling is not working. When I go into the AC settings it says it's already activated (see attached pic) yet I have no on/off button or anything giving me control of it like my girlfriend has on her unrooted, stock G4.
I am rooted on OC3, no roms or anything just stock. But for what it's worth I also could NOT get it to work when I was unrooted either.....
Anyone else having issues?
Factory reset
Same here.
dobbs3x said:
Factory reset
Click to expand...
Click to collapse
Don't wanna lose root and have to do the whole process over again :crying:
I am having the same issue, went through various reset and disable/enable on verizon's end. They are saying the only option left (in their troubleshooting tree anyways) is a factory reset, which I would ideally like to avoid.
Is there any benefit to an on device factory reset rather than pushing the stock OE2 via Odin?
I wonder if I did a factory reset, got AC to work, then re-rooted, if the AC would stick and continue working alright with root? Because I want both...
Ok guys so here's what I did.
I spent a ton of time in a support chat with samsung to no avail.
I finally flashed via odin, OE2 software (which was the out of box software for me) Rebooted and upon noticing that it wasn't a "full wipe" decided to do a factory reset.
Then I booted into recovery and performed the factory reset. At this point advanced calling was still listed as enabled on my verizon account.
I start up the phone, set it up (and deal with the annoying OTA download which I of course did not install) and the DT Ignite app pulls, plus other application updates. Lo and behold Advanced calling is available on my device. I download pingpongroot, perform it, verify it, and now I'm off to the races of getting my device back the way I wanted it.
I have titanium backup installed and I froze the "System Update" program and deleted the update.zip file from ./cache/fota. DT Ignite has also been disabled via the application manager.
I still have advanced calling and have verified it functions properly.
My only slight concern at this point is I have yet to reinstall adaway. Other than that I have performed all the major tinkering I did last time.
Hope this helps.
In short, an OE2 odin pull followed by a factory reset worked fine for me.
- JasonVaritekMVP
JasonVaritekMVP said:
Ok guys so here's what I did.
I spent a ton of time in a support chat with samsung to no avail.
I finally flashed via odin, OE2 software (which was the out of box software for me) Rebooted and upon noticing that it wasn't a "full wipe" decided to do a factory reset.
Then I booted into recovery and performed the factory reset. At this point advanced calling was still listed as enabled on my verizon account.
I start up the phone, set it up (and deal with the annoying OTA download which I of course did not install) and the DT Ignite app pulls, plus other application updates. Lo and behold Advanced calling is available on my device. I download pingpongroot, perform it, verify it, and now I'm off to the races of getting my device back the way I wanted it.
I have titanium backup installed and I froze the "System Update" program and deleted the update.zip file from ./cache/fota. DT Ignite has also been disabled via the application manager.
I still have advanced calling and have verified it functions properly.
My only slight concern at this point is I have yet to reinstall adaway. Other than that I have performed all the major tinkering I did last time.
Hope this helps.
In short, an OE2 odin pull followed by a factory reset worked fine for me.
- JasonVaritekMVP
Click to expand...
Click to collapse
I'm in a similar situation in that I have the same build and rooted. VZW Tech support advised me to use Software Repair Assistant. Does anyone know if this will affect my ability to root again, I mean once it restarts and does any auto updates? Also, does it restore all my data, settings, pictures, etc?
molgen said:
I'm in a similar situation in that I have the same build and rooted. VZW Tech support advised me to use Software Repair Assistant. Does anyone know if this will affect my ability to root again, I mean once it restarts and does any auto updates? Also, does it restore all my data, settings, pictures, etc?
Click to expand...
Click to collapse
I have never used the Software Repair Assistant tool but I'd be pretty wary of using a tool when I don't know exactly what it is doing. I'd hate to accidentally permit something to make my phone un-rootable. If you haven't tried re-flashing OE2 followed by a factory reset I'd give that a shot first.
- JasonVaritekMVP
Hello all.
It's a long story and I will try explain my problem as good as I can.
So it all started a year ago on my other s7 edge. It was rooted and I was running a rom. Loved that one. Not gonne name it because my screen totally burned in with an app. It was due the screen was broken. So samsung gave a new one for free. They didnt even check.
This is where I think things go wrong. I had to wait a bit so my boss gave me his old htc for the time being. So finally I got my new edge. A week or two before npugat update. Now after nougat I notice things are not right. Allot of core apps don't upgrade. So had to do it manually.
Okay no problems. So called help support. They ticked auto update on wifi and mobile a few time. And he told me. My co worker told me about this weird bug. If this doesnt work you need to make a new google acc and samsung acc and factory reset. So I was like hmmm no. Allot of payed apps.
So I was thinking... lets check some stuf. So I activated the dev settings and then backup and restore. And there it was an option called auto restore after a new installation... well my last login was on a htc.
So okay i have tryed allot and here are things I have discovered.
-Core apps are the most early version there are
-If I go to google play store or samsung. The most basic apps like email and clock and so one. It says not compitable with ur device. Even if I update it manually.
-If I want to report stock apps it will always say app id or package name are missing.
-A few app permissions only work.
-I also didnt update a few apps and they had five or more new releases. Still says nope still ot will say its the latest version.
-So software update still works. Last week a new security patch. But really everything is messed up.
-Cant manual update any apps any more. Always app conflict or not compitable.
-So I installed a few device software and hardware info. Radio unknown sdk unkown and so on.
-So finally installed an emulator and runned the command $sh getprop. U can guess allot of unknowns and false and negative settings. With negative it says -1 or -0.....
So im really clueless. I need a real total clean wipe. Reinstalled bl cp and ap and csc.. If I will check off auto restore after new device or restore and flash it with odin. Will this solve this issue?
And what are the proper odin settings and do I need to use the pit file? Cus Somehow the latest update tryed to install core apps on my external sd card... Its a 0 mb card since I dont use a sd card.. But I did had one on my old one.
I hope to get some tips. Because this time I wont flash or root without someone else his advice. Everything I told is in a period of 4 months.
Thnx in advance. Hope to hear soon.
AllSmokeEm said:
Hello all.
It's a long story and I will try explain my problem as good as I can.
So it all started a year ago on my other s7 edge. It was rooted and I was running a rom. Loved that one. Not gonne name it because my screen totally burned in with an app. It was due the screen was broken. So samsung gave a new one for free. They didnt even check.
This is where I think things go wrong. I had to wait a bit so my boss gave me his old htc for the time being. So finally I got my new edge. A week or two before npugat update. Now after nougat I notice things are not right. Allot of core apps don't upgrade. So had to do it manually.
Okay no problems. So called help support. They ticked auto update on wifi and mobile a few time. And he told me. My co worker told me about this weird bug. If this doesnt work you need to make a new google acc and samsung acc and factory reset. So I was like hmmm no. Allot of payed apps.
So I was thinking... lets check some stuf. So I activated the dev settings and then backup and restore. And there it was an option called auto restore after a new installation... well my last login was on a htc.
So okay i have tryed allot and here are things I have discovered.
-Core apps are the most early version there are
-If I go to google play store or samsung. The most basic apps like email and clock and so one. It says not compitable with ur device. Even if I update it manually.
-If I want to report stock apps it will always say app id or package name are missing.
-A few app permissions only work.
-I also didnt update a few apps and they had five or more new releases. Still says nope still ot will say its the latest version.
-So software update still works. Last week a new security patch. But really everything is messed up.
-Cant manual update any apps any more. Always app conflict or not compitable.
-So I installed a few device software and hardware info. Radio unknown sdk unkown and so on.
-So finally installed an emulator and runned the command $sh getprop. U can guess allot of unknowns and false and negative settings. With negative it says -1 or -0.....
So im really clueless. I need a real total clean wipe. Reinstalled bl cp and ap and csc.. If I will check off auto restore after new device or restore and flash it with odin. Will this solve this issue?
And what are the proper odin settings and do I need to use the pit file? Cus Somehow the latest update tryed to install core apps on my external sd card... Its a 0 mb card since I dont use a sd card.. But I did had one on my old one.
I hope to get some tips. Because this time I wont flash or root without someone else his advice. Everything I told is in a period of 4 months.
Thnx in advance. Hope to hear soon.
Click to expand...
Click to collapse
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thanks for the quick response.
Will this clear core apps aswell? And will it apply the "Restore settings and system" after the flash? Since last time I used odin in this way when it says wiping date it instant completed that part.
And about the bootloop. I work for a company I flash software directly on the boards. When u flash directly on a board a bootloop is good and can take up to 20 minutes. Since it have settings who need to be aplied for the next step. And those only get aplyed after a reboot. Does this count for odin aswell perhaps? When it bootloops keep it doing for a while?
Thanks
AllSmokeEm said:
Thanks for the quick response.
Will this clear core apps aswell? And will it apply the "Restore settings and system" after the flash? Since last time I used odin in this way when it says wiping date it instant completed that part.
And about the bootloop. I work for a company I flash software directly on the boards. When u flash directly on a board a bootloop is good and can take up to 20 minutes. Since it have settings who need to be aplied for the next step. And those only get aplyed after a reboot. Does this count for odin aswell perhaps? When it bootloops keep it doing for a while?
Thanks
Click to expand...
Click to collapse
Taking a while to load at first startup is normal, but bootloop is not "normal", sometimes bootloop happens depending on the operating system being flashed but generally speaking bootloop should not happen under normal circumstances when flashing with Odin.
As for clearing your apps, it should automatically format the system partition before it flashes the system.img which "should" overwrite the existing system partition with the new system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
I would try flashing the stock firmware via Odin, download the firmware and place it in the AP slot in Odin with default settings and options, don't change anything in Odin. Then flash it.
If it bootloops after flashing, boot to stock recovery and factory reset/wipe cache in recovery.
If that doesn't work you can try flashing the firmware again along with the PIT for your model number. Place your firmware in the AP slot then find the PIT tab in Odin and place the PIT there, then in the options for Odin, make sure the "repartition" option has a check beside it, then flash the device.
Again, you might have to boot to recovery after flashing to wipe the device if it bootloops after flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Droidriven said:
Taking a while to load at first startup is normal, but bootloop is not "normal", sometimes bootloop happens depending on the operating system being flashed but generally speaking bootloop should not happen under normal circumstances when flashing with Odin.
As for clearing your apps, it should automatically format the system partition before it flashes the system.img which "should" overwrite the existing system partition with the new system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Ahh okay. Will do you steps then. Hope it will work. I do have one last question.
I've just read before you flash. You have to remove all securitys like fibgerprint and accounts. And after the flash when you get at the setup. They say skip all. And add everything after so it wont restore old stuff. Is this true?
AllSmokeEm said:
Ahh okay. Will do you steps then. Hope it will work. I do have one last question.
I've just read before you flash. You have to remove all securitys like fibgerprint and accounts. And after the flash when you get at the setup. They say skip all. And add everything after so it wont restore old stuff. Is this true?
Click to expand...
Click to collapse
I don't have a Samsung device that requires these steps but it sounds like solid advice to me though. It sounds right because doing it that way means you're signing into the device without associating it to anything from before to let it complete setup without issues and then setting everything up after. Then if any of the things you re-associate cause issues, it will be easier to resolve than it would be if you flashed and restored everything during setup, doing it that way makes it hard to fix things because if something doesn't work it can cause your device to not boot properly. Doing it the after setup avoids some of those issues.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
I don't have a Samsung device that requires these steps but it sounds like solid advice to me though. It sounds right because doing it that way means you're signing into the device without associating it to anything from before to let it complete setup without issues and then setting everything up after. Then if any of the things you re-associate cause issues, it will be easier to resolve than it would be if you flashed and restored everything during setup, doing it that way makes it hard to fix things because if something doesn't work it can cause your device to not boot properly. Doing it the after setup avoids some of those issues.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Okay.
Thanks allot for taking time and the great advice. Gonne follow it up and after that I might gonne install magisk su. Never heard about since last night. Will let you know the results.
Edit
Thanks sir.
As what I can see for now allot of my issues are fixed. Probaly need to test more. But like they say time will tell. Great support much appreciated. Next steps twrp superstock kernel and magisk.
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode
I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.
halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk