Related
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Sportsmaniac13 said:
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Click to expand...
Click to collapse
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Skipjacks said:
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Click to expand...
Click to collapse
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Sportsmaniac13 said:
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Click to expand...
Click to collapse
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Skipjacks said:
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Click to expand...
Click to collapse
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Sportsmaniac13 said:
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Click to expand...
Click to collapse
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Skipjacks said:
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Click to expand...
Click to collapse
Okay. Thanks for the help anyways, I appreciate it.
Sportsmaniac13 said:
Okay. Thanks for the help anyways, I appreciate it.
Click to expand...
Click to collapse
OK, you've been moved to the Verizon forum.
The OTA failing quickly as you describe usually means that one of the files that the OTA is trying to update has been modified.
What you should do is figure out what build your phone is running (Settings, More, About phone, then look at "Build number").
That will tell you what you need to flash to restore the phone to stock, hopefully with a no-wipe image.
Thanks for all your help guys. I finally solved the issue, so I figured I'd post how I did it in case anyone else runs into something similar.
I actually updated the phone through Verizon Software Upgrade Assistant. I'm assuming that through doing this I flashed the phone back to stock. Once this was over, the phone notified me of another update, and this time everything went smoothly. The phone is now completely stock and completely up-to-date.
So if anyone has a similar problem, give Verizon Software Upgrade Assistant a shot.
So, I rooted my phone, went to ROM Manager and pressed...something (not sure what). My phone then rebooted automatically and said "Custom binary blocked by Reactivation Lock". I gather this is because I didn't click some option on my phone before it restarted.
So then I started looking for ROM's or anything to bring the phone back online. I downloaded Odin and tried installing a ROM and I get "Custom Binary(RECOVERY) Blocked By R/L"
So now, I'm trying to download the stock firmware but, the problem is...I have no clue which firmware to use. I don't have access to much on my phone other then what I can see on the back of the phone.
SM-G925I UD
My provider is GCI out of Alaska and my phone is unlocked from the store. Which firmware do I use because from what I've read, SM-G925I is an international version and I'm not sure which I should use.
One thing to note...I'm the worst nerd ever when it comes to this. Thank you so much for any help you guys can give.
I did the same thing...
chauffeurtim7 said:
So, I rooted my phone, went to ROM Manager and pressed...something (not sure what). My phone then rebooted automatically and said "Custom binary blocked by Reactivation Lock". I gather this is because I didn't click some option on my phone before it restarted.
So then I started looking for ROM's or anything to bring the phone back online. I downloaded Odin and tried installing a ROM and I get "Custom Binary(RECOVERY) Blocked By R/L"
So now, I'm trying to download the stock firmware but, the problem is...I have no clue which firmware to use. I don't have access to much on my phone other then what I can see on the back of the phone.
SM-G925I UD
My provider is GCI out of Alaska and my phone is unlocked from the store. Which firmware do I use because from what I've read, SM-G925I is an international version and I'm not sure which I should use.
One thing to note...I'm the worst nerd ever when it comes to this. Thank you so much for any help you guys can give.
Click to expand...
Click to collapse
I have same phone, same carrier, and after rooting I was messing with different options and ended up with the same error message. After several hours of searching, trying different methods without success, I found a video on youtube called, "Samsung Smart Switch for PC Flashing Firmware to Galaxy S6 Edge" and I was able to reflash the phone to the stock firmware using the emergency recovery option "Device Initialization". I had to put in the s/n of the phone, hopefully you still have it on a label somewhere. Anyway, after the restore, it was upgraded from 5.0.1 to 5.1.1. and the Carrier boot animation was gone. Now time to re-root!
Hopefully you find a successful solution to your issue, good luck!
I want root without the problems
Bricked6 said:
I have same phone, same carrier, and after rooting I was messing with different options and ended up with the same error message. After several hours of searching, trying different methods without success, I found a video on youtube called, "Samsung Smart Switch for PC Flashing Firmware to Galaxy S6 Edge" and I was able to reflash the phone to the stock firmware using the emergency recovery option "Device Initialization". I had to put in the s/n of the phone, hopefully you still have it on a label somewhere. Anyway, after the restore, it was upgraded from 5.0.1 to 5.1.1. and the Carrier boot animation was gone. Now time to re-root!
Hopefully you find a successful solution to your issue, good luck!
Click to expand...
Click to collapse
I have the same phone with the same carrier; I live in Anchorage. I haven't done much tinkering yet because I don't want to break my phone, but if this works-- I would really like to be able to root my phone and upgrade it to Marshmallow when it becomes available. Can either (or both) of you confirm that this method did work for you to get the SM-G925I rooted and working again with GCI?
Thanks!
---------- Post added at 02:57 AM ---------- Previous post was at 02:51 AM ----------
[/COLOR]here is the firmware for the s6 edge g925i that i could find on the firmware section ..http://www.sammobile.com/firmwares/database/SM-G925I/
Just download samsung kies on your computer, put your phone in download mode and then do a emergency software recovery (can be found from some option on samsung kies)
Have any of you other Alaskans with GCI successfully loaded Marshmallow onto your G925I? I managed to root my S6 Edge successfully using CF-Autoroot but I am hesitant to try and flash another firmware from Chile, or Uruguay, or India etc onto the device because I'm worried about disabling the radio or other region specific settings that will cause my phone to lose connectivity. I have made a full backup using Flashfire and backed up other relevant data but I would rather know about others' experiences before I recreate the same problems that have already been done over and over again. None of the firmwares available on sammobile.com seem to match up with what I have now (I attached a picture of my current firmware).
Any help or experience is very much appreciated.
Nougat and Going Strong
I'm just providing an update since there aren't a lot of links to S6 Edge and GCI Alaska on XDA. Since this phone is starting to get a little older and I had been successfully running Marshmallow for a year or so I decided to push my luck and see if I could get Nougat running. I'm very happy to say that after a couple of failed attempts with some other versions not running well, I installed Samstock 7.0 using the install instructions on https://forum.xda-developers.com/ga...unified-development/rom-samstock-rom-t3649798 and I am pleased to say that it is running very smoothly and I am happy that I did so. I had pretty awful battery life with it at first, but after installing Root Booster and setting the basic battery saving option I am back to 24 hours or so between recharges. I couldn't be happier that this device which shipped with Lollipop has been upgraded all the way to Nougat and is still going strong.
Hi all,
I am stuck. Here is my sad story.
I have an ATT S7 that I was attempting to load the S7 Tmobile image using Odin. After hitting the encryption error in odin, my searching led to the PrinceComsey version and that got around that problem. I then hit a Fail(Auth) error and tried a few other suggestions that I found. The last part I tired as ticking the "update phone bootloader" option. Odin failed again, this time, the phone was stuck in recovery menu loop. I tried to clear and restore to factory settings, but couldn't get out the loop. Finally, it stopped booting the base menu and now I get the wonderful blue screen exclamation mark that tells me I need to use Samsung's Emergency recovery. I can't even turn the device off now. The only other thing I can get it to do is to get to the download screen.
From all I have read, it seems the next step is to upload a valid stock image with Odin and that should be that. So that's where I am stuck. I have tried a couple different images, but they all fail in one way or another. I think what I need help with is figuring out which image is the right one to install. At this point I just want to get back to a working phone, so an ATT image is fine for now, but would ultimately want to get to a Tmobile image now that I have switched carries.
Any help is much appreciated!
Use smartswitch to restore stock software.
Also, try to use the right forum , you probably get more help
Oh dang... I claim temporary insanity for putting this in the S6 forum. ugh.
In any case, thanks for the response. I got it all figured out. Here are some tidbits in case it is helpful to someone in the future.
1) Yes I tried the emergency recovery using smart switch. It turns out that you need the device serial number. It also turns out that on my ATT supplied S7, there is no s/n etched on the back. And just for laughs, it isn't even printed on the original box. So if you do not have it written down and your device isn't functioning. You are SOL.
2) After several failed attempts, the magic formula was the modified Odin and the Jan'17 SM-G390T build that I found. I selected all four files for flashing and the n-th time was the charm.
3) I am now running the Tmobile build of Nougat on my ATT S7 with everything working as it should. That includes the phone using the tmobile signal booster that the ATT build couldn't find and has wifi calling available. It is exactly as I wanted.
Hello, I am new here and I made a huge mistake!
I purchased Samsung Galaxy Tab S6 Lite (LTE) literarally 1-2 days ago and I wanted to root it, I had my smart phone rooted which did not have Knox protections, it was as straight forward as flashing TWRP and use Magisk via instructions I followed.
I make use of "Root" privileges a lot when using my device, I find it very important to my daily life so I decided to risk rooting it, after doing so my tablet was showing 2 errors, that its not using official samsung software and that the boot loader is unlocked, when I unlocked the boot loader using OEM Unlock everything went fine, the option was greyed out and checked afterwards.
During the boot process, it reboots 2 times and it shows a integrity error, integrity and some very long number, I am assuming its a integrity check? I have the exact matching firmware, so I flashed back the stock firmware and... the "not using official samsung software" warning disappeared, it boots me into recovery mode, I choose "reboot" and the device goes to boot looping with the same error.
I was following this tutorial: https://forum.xda-developers.com/galaxy-tab-s6-lite/how-to/howto-unlock-root-galaxy-tab-s6-lite-t4132289
But there are some things I skipped, here the exact steps I took:
Unlocking Boot Loader:
Followed all the steps from 1 to 4 but I skipped the 5th step entirely, the step where it asks you to mess with firmware date and twrp, I did none of that, I will mention that when I was looking for stock firmware to download before doing anything, I was not able to understand the CSC so I didn't know which firmware to exactly use until a software update came up which told me the exact firmware, I accepted the update and download that stock firmware, because my firmware was updated I didn't think that following the few steps of the step 5 would've done everything as I was already off the path.
I didn't do the 6th step as I just checked of the OEM Unlock is greyed out and still checked in the "developer options" section, I assumed that it was a success, not to mention the boot loader unlocked warning that was showing up and yes, all the data was erased and was forced to go through the setup process again as expected.
Root the tablet:
1. I have downloaded the firmware as it says not just for the purpose of rooting, the firmware that the software update told me about, this is the firmware I downloaded, the firmware is a exact match, everything is matching: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
2. I follow all the steps from 2 to 11 from here.
3. When I reached step 12, I went to download mode and I look for any messages regarding it only allowing for official samsung images, but I saw no such message, didn't really pay attention to anything else, I just glossed over things, considering there was no such message I assumed that KG/RMM state was good, don't know what it was but it might not have been "prenormal" because there was no message regarding official samsung images, from here I falshed the boot.tar file like in the instructions, that lead me to my current problem I mentioned at the very start of this post.
4. There was no step 13 as I can't boot into android due to "integrity" error I have, right now I have my tablet turned off (thank god I can do that) via the recovery that shows up after flashing stock firmware.
Addition Info:
1. I don't have any data to lose, if I need to do a factory reset or something of that sort, I have no problems doing that.
2. As I mentioned at top, I do have a stock firmware downloaded from this link here: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
3. The tablet is: SM-P615 (Samsung Galaxy Tab S6 Lite (LTE), I bought the LTE so I could use it as my phone)
4. At the download mode, the OEM (Boot Loader) state is set to NO and the FFS (I don't remember if its FFS exactly at the moment, something FF I believe, I don't want to turn on my tablet at the moment) was set to NO.
5. The KG (No RMM mention that I could see anywhere) state is showing up as "Checking..."
What do I need to do to fix my tablet? do I need to wait for 7 days? if so how do I do so, like does leaving my tablet off count or not?
PS: I am a self-thought experienced low-level windows programmer, I've been doing programming for over 10 years now, never have worked with Android development but I can attempt to build something from source if necesarry, I know very little about Linux OS as I purely work with Windows and use Windows for everything including servers.
I have done some research regarding that "integrity" error and I can't find any screenshot in google images that matches how it looks on my screen, but there are a lot of them quite similar to it, which basically says "verification failed, factory data reset your phone", in my case I don't have that message, it just says "integrity", but when the boot looping stops and shows that failure I do have 3 options, "try again" and "Factory data reset" and the 3th one I don't remember, I am suspecting that this could be my problem! I believe the samsung just changed the way that particular message is shown (visual change), so I just need a factory data reset and it will work, most likely with the rooted boot.img file! I will attempt this after a few hours of this reply, I may have panicked too early.
The issue has been fixed
Well this is surprising, I was about to do the factory reset but before doing so I decided to flash the same magisk patched boot.img file, when I flashed I saw seeing those 2 warning messages as expected, I was expecting for it to fail after 2 boot loops so I can do the factory reset as intended but on the 3th boot loop the tablet booted up! I was brought at the android setup screen, once I was done with that I checked the OEM Unlock, it was still checked and greyed out, downloaded Magisk Manager and to my surprised it worked! Magisk Root latest version is installed and working, it asked me to allow magisk do some "additional setup", the tablet booted up perfectly fine after that "additional setup", I check root privileges using "Root Checker" and it worked, I have root privileges! I most likely have panicked too soon, sorry for wasting your time! Hopefully this post will be useful to someone in the future looking to root their tablet.
My assumption of what happened: When I flashed the stock firmware AP a second time so I can turn off my tablet, it most likely did a factory reset without me knowing, so when I flashed magisk again before letting it try boot up again, the tablet booted perfectly fine because factory reset has already occured, which brought me to the android setup screen.
Hello XDA community,
I have a G965F that is permanently stuck on the first boot screen (Samsung Galaxy S9+ secured by Knox powered by Android) and it will not progress past this point. I have left it on for hours, and it just stays on that screen. Recovery mode does not work; if I try the button combination for it, it just stays on the same screen as mentioned before. However, I am able to get it into download mode. From here, I have tried flashing every firmware I possibly could, of course with the correct region and version, but nothing works, and the situation stays the same as mentioned before. Odin usually finishes up with no problems and reboots the phone, in which case the bootloop happens once again. On the rare occasion that Odin does fail, it will not boot even to the first splash screen but rather to the blue screen with the triangle, telling me to connect it to SmartSwitch and go from there. I have attempted this also, but SmartSwitch only gives some errors, and it fails.
The phone was on the stock firmware for a few years and even updated through Odin when OTA didn't work. It is a UK-unlocked Exynos device. About 2 years ago, I decided to switch to lineageOS using Neuroticals ROM, and that worked flawlessly, OTA updates and everything, 0 problems. I even went back to stock at some point and reinstalled Lineage shortly after because of how much it improved the device. About 9 months since I last did any type of flashing, the phone randomly froze while I was using it (I think the bottom half of the screen went black) and was totally unresponsive until I forced shut it down. This is where the aforementioned problem began.
I thought letting the battery run out would help, but it hasn't. One thing I have noticed is that it either charges very slowly or doesn't at all; it will only stay on for a maximum of a minute after it is unplugged. I left it for a few months, hoping to discharge it completely, but the problem persists.
Apologies for the lengthy post; I've used this site for about a decade for mods on various devices and it has solved all of my problems, but this is the first one that has really stumped me. For the past few months I've spent tens of hours searching various forums and webpages but can find very little about my specific problem. Thank you for any help in advance.
I will include pictures of the codes that download mode shows, and hopefully someone has some answers.
PS. For some reason current binary says "Custom (0x8)" after successfully flashing the stock firmware many times with Odin, but when Odin does fail it will show "Samsung Official". This I cant make heads or tails of.