I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
SirMilkaPeach said:
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
Click to expand...
Click to collapse
This just happened to me and I the problem was that I had Secure Startup enabled under Lock screen and security. I just disabled it and re-rooted it and that fixed the problem. Hope it works for you.
Related
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly
Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.
Hi everyone,
Right I have a serious issue with a 4 day old S6 from the UK bought SIM-Free off Amazon.
My phone was rooted but didn't have ADB or any sort of custom recovery. I edited the build.prop file for the RAM management thing, and created a copy back up on my storage. I didn't like it too much, so I copied the back up over the edited one and restarted - phone went into boot loop.
I have attempted to use Odin and flash a stock firmware ROM (had to settle for a H3G variation because the XEU unbranded was off some download website that takes 10 hours to download). I went through all the steps with Qbking77's walkthrough with Odin and it came up that it failed at the end.
The phone then booted into the Emergency Recovery screen, and couldn't get back into Recovery (to do the Smart Switch recovery), and can only get back into the Download bit.
I've tried flashing it again, and no avail.
I seriously, seriously hope someone can help me out here, it's a brand new phone and I love it and I don't want to be left with a brick.
Thanks.
I was in the same boat, if you rooted and didn't trip Know, your best bet is the Samsung Store, they're all over the UK
Well an update:
After the third time flashing failed, I did a root via Odin which had previously failed, and it booted up, completely normal and set up the device as normal.
I have no idea how that worked - but it did. Probably tripped the Knox I think but it works.
I was able to install the first of the two updates earlier for the 5.1.1 update on my Verizon Galaxy Note Pro 12.2. The second downloads, prompts for install, reboots and begins installing but errors out and reboots back into the OS home screen. The Verizon software update manager shows Failed software update error code 402. I have factory reset my tablet a couple of times and still same issue. I do not have my tablet rooted and no apps disabled.
I downloaded the latest available Samsung firmware md5 file, version VZW-P905VVRUANK1-20141205133604 and tried flashing using Odin 3.07 while in download mode. It starts and after a few seconds, Odin fails and on the tablet screen, I get the error, SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I have re-downloaded the firmware along with older versions and still same issue.
I was reading somewhere that my tablet could be "soft bricked" and that is why it will not install the second part of the OTA. As for the Odin/download mode error, I had read that the firmware version I am trying to flash in Odin has an older version of bootloader than my current and Samsung does not let you downgrade the bootloader. I may be wrong on both accounts, which is why I am seeing if anyone else has had this same issue or have any advice on what I can try.
Thanks in advance!
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
dansto82 said:
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
Click to expand...
Click to collapse
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
tdetroit said:
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
Click to expand...
Click to collapse
I was able to get mine to update using ODIN and the firmware file from sammoble. Factory reset on the tablet, factory reset in recovery and finally ODIN worked.
I was having the same problems as the OP listed. Once I decided to live without root and I would be okay with wiping the tablet, I performed exactly what dansto82 said he did and I'm now on 5.1.1.
Now hoping someone comes up with a way to root.
Hey, I have the p905v and it is running 4.4.4, I rooted it with towelroot and it was completely fine. I then tried putting twrp recovery on it the wrong way through flashify and now I don't have a recovery mode and can't update it to 5.1.1. Other than that the tablet runs perfectly fine. Is there a way I can fix it?
Sent from my SM-P905V using XDA Free mobile app
Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
jfm91 said:
Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
Click to expand...
Click to collapse
Factory reset from recovery?
Yes. full wipe on everything
jfm91 said:
Yes. full wipe on everything
Click to expand...
Click to collapse
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
*Detection* said:
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
Click to expand...
Click to collapse
After you replied I tried to flash again.
Flashing took 3 mins.
After that the phone went straight to boot loop. I have now waited 15 minutes, and still no boot. The screen have turned black, and blue led indicator is on
Sounds like something else is wrong if it still loops after flashing CSC, that contains the PIT file, which repartitions the phone, and also resets it
Got a MicroSD card in? Try removing that in case it's faulty, otherwise hopefully someone else has some ideas
Could try flashing the Nougat Beta as a test
I have removed SD-card. (Have it in my backup phone now.)
Could it be hardware issue?
I'm considering to contact my insurance company, for a new phone
Could be, but sounds more like a firmware issue
Tried Smart Switch firmware recovery?
*Detection* said:
Tried Smart Switch firmware recovery?
Click to expand...
Click to collapse
Doesn't help either
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Problem is that I have "custom binary count"
jfm91 said:
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
Click to expand...
Click to collapse
Mabey you should try flashing an older firmware like PE1 and then updating later!
http://www.theandroidsoul.com/download-galaxy-s7-firmware
using Odin but first try only flashing the AP, CP, and CSC don't do the BL. If that fails then try doing a flash with the BL included. Hopefully this works!
If worst comes to worst, if your knox isn't tripped, then send in or warranty.
Did you put a custom recovery on it?
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
jfm91 said:
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
Click to expand...
Click to collapse
better question. Can you last on your old phone til Galaxy 8 comes out for sale?
Alikhan821 said:
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Click to expand...
Click to collapse
Did you manage too solve this issue ? I am facing the same problem.
Cheers
Hi,
Samsung repaired the phone for me so the issue was solved.
Do you remember what the issue was about and how much it costed you ?
Thanks.
Since the phone was in warranty and I never rooted it, it was repaired for free. They arranged to come collect it from my house and I had it back within 3 days. They replaced the motherboard in my case.
Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks