Related
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
rleighska said:
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
Click to expand...
Click to collapse
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
recovery
rleighska said:
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
Click to expand...
Click to collapse
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
Iceburn1 said:
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Click to expand...
Click to collapse
Any help is appreciated!!! I have no idea what to do next. I've done and re-done everything possible. For whatever reason it won't let me boot into recovery. It just goes straight to the Samsung screen with the warranty bit kernel at the top. I just reflashed the stock firmware and it booted up to the samsung screen showing "recovery booting" and "set warranty bit : recovery" at the top. If I flash a recovery (through odin, the same way I flashed the firmware) it will boot to the same screen, but will say "set warranty bit: kernel" instead, but will not go past that screen. I've tried several recoveries, all of them take me to the same screen when flashed. I feel like I'm in a boot loop myself with the things that I've been trying to get this thing to work.
A friend of mine said when I'm at the point that I'm on the samsung screen with the "set warranty bit: kernel" I should be able to boot to download and flash a stock kernel through odin. I haven't found one kernel file that worked. Every one I've tried either gives a md5 binary error or makes odin freeze and close.
I don't think I was using ART. When I got the phone all I did was root it, didn't even get a good ROM on it yet, but then again, I'm not exactly sure what "ART" is because I'm not 100% familiar with all of the terminology just yet, but I'm learning (or trying to).
At this point all I want to do is get it back to stock and re-root it.
Or, if there was a way to reinstate my warranty with Sprint, I'd take it back to them and get a new one.
s5 fix
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Iceburn1 said:
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Click to expand...
Click to collapse
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
xposed installed or gravity?
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
Click to expand...
Click to collapse
I think I did have xposed installed and gravity come to think of it. I tried holding volume down and power and it went to the samsung screen with:
recovery booting.....
recovery is not seandroid enforcing
set warranty bit : recovery
If I turn off, go back to download mode, flash recovery, let it reboot, it will then still be stuck on the samsung screen, but will have:
set warranty bit: kernel
I have not yet found a kernel that will flash successfully and I can't get it to go into recovery at all, just download. It keeps getting stuck on the samsung screen with either the set warranty bit : recovery, until I flash recovery, then it says set warranty bit : kernel.
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Click to expand...
Click to collapse
I'm not sure if I was on ncb or nd2. How do I tell? When I got it I rooted it with CF- auto root, but I didn't do anything else to it that I can recall. I was going to install a rom, but the file wouldn't transfer for me, so I gave up on that until there were other roms to try. The only other thing I did once rooted was download titanium backup, did a backup of everything, downloaded xposed, and was using some of the modules from there. I was using twrp recovery and now I can't get anything to come up that even says twrp.
rleighska said:
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
Click to expand...
Click to collapse
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Nyc1231 said:
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Click to expand...
Click to collapse
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
safemode
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
rleighska said:
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
Click to expand...
Click to collapse
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Nyc1231 said:
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Click to expand...
Click to collapse
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
xposed and gravity
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Iceburn1 said:
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Click to expand...
Click to collapse
I can't get it to boot to recovery. When it starts it shows the kernel message at the top in yellow, the samsung logo etc. and will not move from that screen. The only other thing I can do is put it in download mode.
safe mode
Safe mode is different from download and recovery it boots you into phone so u can disable xposed or gravity lossiboy the cause
rleighska said:
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
Click to expand...
Click to collapse
Have you try using different version of odin when restoring to a stock firmware?
Sent from my SM-G900P using Tapatalk
Iceburn1 said:
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
Click to expand...
Click to collapse
I tried that and it still goes right to the samsung screen with
recovery booting.... in blue
set warranty bit : recovery in yellow
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
chewtoy0 said:
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
Click to expand...
Click to collapse
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
mrd0pe said:
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
Click to expand...
Click to collapse
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
chewtoy0 said:
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
Click to expand...
Click to collapse
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Your S/N is on the rear of the phone it can be a pain to see but it is there. Use smart switch to restore the firmware. Just click emergency firmware restore.
It is? The IMEI is there but I didn't see the SN. Also my phone is black so that doesn't help.
I will have another look.
mrd0pe said:
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Click to expand...
Click to collapse
I did that. No dice.
I had the same issue as you. Used the same rom and disabled developer options. I downloaded stock firmware.. flashed it with odin. It actually took 2 tries. The first time I could see only 1/4 of the screen. The second time i flashed stock firmware from another country and it worked. You might actually have to do a hard factory reset if you cant unlock your phone.. for some reason. Then I let kies do its magic because I could then see my S/N. Right now I still feel my phone slightly different. Messenger is unstable for some reason also.
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
chewtoy0 said:
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
Click to expand...
Click to collapse
Try to flash Nougat firmware, as that was what your custom rom was on right? I dont think it really matters though as I downgraded from stock 7.0 to stock 6.0.1 via odin without errors... But you can try
As an absolute last resort I would try to check the "re-partition"-tab and provide odin with a .pit file, then load everything (BL, AP, CP...) with stock firmware <<<< do this at your own risk, if you are not careful, your phone will be bricked
I am trying to flash MM back to it .
I'm not sure I want to mess with the re partition table...But it's already soft bricked.
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Matty39856 said:
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Click to expand...
Click to collapse
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
chewtoy0 said:
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
Click to expand...
Click to collapse
I'm not sure then. Have you tried flashing the latest unlocked version for your region? I remember on my s6 I had a similar problem that was caused because I was trying to flash a lower version of Android than what I previously had. So ended up flashing the latest unlocked version BTU for my region and it worked. Sorry I can't be of more help. It looks like the latest firmware is still 6.0.1 that's why it's blocking it from downgrading.
Was sent a PM by a person. Was skeptical at first, but in 10 minutes using TeamViewer, they fixed the issue by reflashing the device (as well as repartitioning it properly). I can't thank them enough.
This is the person on Facebook...
Unlock Network FRP Lock Remote Service
Hey guys, I really screwed up big time with my S7. My model is the SM-G930F. I have numbered my mistakes below so it is easier to follow.
1) I wanted to root my phone, so I followed the guide for HighonAndroid on youtube.
2) Fast forward, got TWRP and flashed Magisk root v16 and samsung anti-root removal 2.4.
3) Restarted phone and got this message along the lines of "integrity of phone has been damaged... please factory reset"
4) I advanced factory reset, and also accidentally ticked the software reset as well :crying:
5) Phone is bricked, and stuck in bootloading error. Cannot be turned off, it would just continue to recycle the Samsung S7 screen on repeat until put into TWRP mode...
6) Can only assess download mode and TWRP mode
If you are still following, this is where I am stuck ATM. I just want a working phone at this point...
7) Download official 7.0 nougat software for my phone model.
8) Odin the firmware over however the message stays stuck at this: https://imgur.com/a/UMQPw
9) Cry
If anybody can help that will be great, thanks!
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
audit13 said:
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
Click to expand...
Click to collapse
The phone stays connected, but the second I flash my phone just reboots.
You're not flashing BL, CP, and CSC?
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yes I got the file from sammobile. I have tried flashing the 4 files however alas, it again just reboots my phone. I will follow up with an image when I get home and try it out again.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yeah here we go: https://imgur.com/a/FF0Rd
Still does not work. It continues to reboot. Tried different computers the phone will just reboot. Is there any hope left? I can access TWRP, meaning is it possible to restore/flash a backup from another user?
You can try Smart Switch which is the official method of a factory flash.
Otherwise for Odin if I recall correctly the latest firmware will chuck a fit if you aren't flashing the right firmware for your country, since the DRAG bootloader is meant to be more locked down.
You could also try different Odin versions maybe https://forum.xda-developers.com/showthread.php?t=2711451
You could try a stock ROM flash via zip like super stock or superman choosing clean install. Would be easier than trying to orchestrate a backup from someone.
Is there any errors that I have now seem consistent with anybody else's issue? Something like I might be flashing the wrong firmware into my phone, as a result the phone just reboots in download mode?
I have tried using both the new and old versions of odin and it still has the same result.
I am using the phone model SM-G930FZDAXSG
Really thanks a lot guys. Just having you guys readily available took a lot of stress off my chest. Someone cares
The issue has just been resolved! Yey. The problem was not running odin in administrator mode. As a result, my phone would just reboot instantaneously after flashing.
Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.
Andre369 said:
Good day everyone. I am totally new to this and on here but hope is something I came with and will always be a part of my beliefs.. I did flash my Samsung S7 SM-G930F a couple of times with different kind of custom ROMS and I guess I upgraded the bootloader by doing so... So now I was in TWRP mode and without thinking, I started to change the DATA format and immediately switched it off when I realized what exactly I'm doing and now it's stuck. It can switch on only with a charger and by force but I am capable of getting into download mode. I am trying to flash a stock ROM but it keeps on failing cause of the bootloader. When I use the PIT file, it shows successful though. But nothing more happens. Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.
spawnlives said:
I don't own an S7 so maybe not much help.
From screen shot above try using Odin version 3.13.1 or higher.
Can you post a screen shot of download mode and Odin when it fails
If you can still get into download mode there should be a line saying AP SWREV: B:? K:? S:? or something similar.
The B:? is your bootloader version number. You will need to flash firmware with this number or higher.
Click to expand...
Click to collapse
Thank you for the response I managed to get it fixed. I used odin 3.14 instead and I wiped it with the NAND option and started from scratch. I used the pit file and flushed the bootloader first with repartition, then did the AP separete, and thats how I went on. After all, I'm back again. Thank you for trying, much appreciated.