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
Related
So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?
rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers
lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility
Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".
The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers
Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks
Thanks in advance to anyone who can help me. So I'm new to rooting and new to xda, I looked around the forums a bit but am unable to find exactly what I'm looking for. I have a Sprint note 3 smn900p. I successfully rooted it using towelroot and confirmed with root checker. I then downloaded Rom manager and used it to download cwm. Here is where I need help, I boot up my phone and this is what I get. (Volume down, home button, and power)
Odin mode
Smn900p
Samsung official
0x0
0x1 (towelroot did not trip this, it was either RM or CWM)
Qualcom secure boot enable (csb)
Rp swrev s1 t1 a1 a3 p1
Write protection enable
Udc start
At the bottom it says "downloading" and "do not turn off target"
That's where it stays and the only way to get rid of it is to do a battery pull.
Now if I hold volume up, home button, and power this is what it says.
Recovery booting
recovery is not seandroid enforcing
Set warranty bit enforcing.
Phone then starts up normally.
I am trying to do all of this without a computer because I don't always have access but any help at all is appreciated. The main reason I am rooting is to get free wifi tethering for my note 10.1 and after that possibly getting rid of the bloatware and overclocking the cpu.
Again thanks to all the developers and anyone else who makes this possible. You guys (and girls) rock!
nycemt said:
Thanks in advance to anyone who can help me. So I'm new to rooting and new to xda, I looked around the forums a bit but am unable to find exactly what I'm looking for. I have a Sprint note 3 smn900p. I successfully rooted it using towelroot and confirmed with root checker. I then downloaded Rom manager and used it to download cwm. Here is where I need help, I boot up my phone and this is what I get. (Volume down, home button, and power)
Odin mode
Smn900p
Samsung official
0x0
0x1 (towelroot did not trip this, it was either RM or CWM)
Qualcom secure boot enable (csb)
Rp swrev s1 t1 a1 a3 p1
Write protection enable
Udc start
At the bottom it says "downloading" and "do not turn off target"
That's where it stays and the only way to get rid of it is to do a battery pull.
Now if I hold volume up, home button, and power this is what it says.
Recovery booting
recovery is not seandroid enforcing
Set warranty bit enforcing.
Phone then starts up normally.
I am trying to do all of this without a computer because I don't always have access but any help at all is appreciated. The main reason I am rooting is to get free wifi tethering for my note 10.1 and after that possibly getting rid of the bloatware and overclocking the cpu.
Again thanks to all the developers and anyone else who makes this possible. You guys (and girls) rock!
Click to expand...
Click to collapse
You use Volume DOWN+Home+power button to flash firmware by USB using Odin program or restore original firmware using Samsung Kies.
The only way you can exit the Odin mode is remove the battery or after having successfully flash a firmware.
You use Volume UP+Home+power button to enter recovery mode. In recovery, you may be able to perform:
- backup of the entire OS and data of the phone.
- recover from a backup in case you encounter any problem flashing a custom rom, etc.
- perform a full wipe or factory reset
- install custom rom or firmware file saved on phone memory or external SD card.
You may use ROM toolbox to remove unwanted bloatware and overclock or underclock your device.
Please hit thanks if I helped.
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Did you install CWM?
nycemt said:
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Click to expand...
Click to collapse
It's not clear from your post whether your really installed CWM recovery. Use Odin (download mode) to flash tar.gz version of CWM (or TWRP). Search for the links yourself. Then you can enter CWM with vol up+home+power combo.
There on, you can flash any (other) recovery or ROM from phone itself via CWM (or TWRP or Philz).
nycemt said:
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Click to expand...
Click to collapse
Yeah, it is possible to flash ROM using your phone memory or external SD card thru Recovery mode (Vol UP+Home+Power).
I suggest you use [root] Mobile Odin Pro (this can be downloaded on play store) if you want to flash kernel/ROM without going to recovery mode. It is also safer to use than flashing in download mode.
For a more user friendly recovery, try using Team Win Recovery Project (TWRP).
It is touch-based recovery. Easier to use.
Please hit thanks if I helped.
Ok so I'm going to download twrp, if I did in fact download cwm will these interfere with each other. Also once I download twrp do I have to open it on my phone or just flash it through recovery mode or through mobile Odin pro. (Sorry for the basic, probably stupid questions)
nycemt said:
Ok so I'm going to download twrp, if I did in fact download cwm will these interfere with each other. Also once I download twrp do I have to open it on my phone or just flash it through recovery mode or through mobile Odin pro. (Sorry for the basic, probably stupid questions)
Click to expand...
Click to collapse
I flash mine using mobile odin. It will replace CWM.
Download the TAR file save it on your external SD.
Open odin.
Grant superuser request
Open file...
Select TAR file
Flash firmware
Your phone will reboot in recovery.
Ok so I bought Mobile odin pro from the play store now if I want to flash a Kernel to my device I would need to find it on here and then download it correct or I could find a rom with the kernel already on it and flash the whole thing and would I be able to find it on mobile odin or rom toolbox? Thanks again you guys are so helpful taking it baby steps with me.
What I meant on my previous post was I flash my recovery which is TWRP using mobile odin.
I suggest you flash TWRP recovery first using odin. Perform backup in TWRP before flashing any ROM in case anything goes wrong, you may be able to go back to the original state of your device.
nycemt said:
Ok so I bought Mobile odin pro from the play store now if I want to flash a Kernel to my device I would need to find it on here and then download it correct or I could find a rom with the kernel already on it and flash the whole thing and would I be able to find it on mobile odin or rom toolbox? Thanks again you guys are so helpful taking it baby steps with me.
Click to expand...
Click to collapse
defiantly follow the previous reply and backup first (very important).
i personally dont download roms etc from apps. i prefer to find it manually on the forum, so you know you have the correct, most up to date file for your device. also, you can read other users post to get an idea of how its working and the possible problems with it.
Ok sorry I took soo long to respond, work has been busy. So I Bought Wifi Tether Router for $2.50 which is still better than 10 extra dollars a month. It works, granted it takes a long time to start up and im not using the stock tether that is included with the phone which would have been great but it gets the job done and I have no complaints. This was one of the main reasons I wanted to root my phone. Anyway I guess when I have some more time to mess with it I will try flashing roms/kernels (I am just soo afraid of hard bricking my phone) but you guys gave some pretty clear instructions so I don't think I'll have a problem. As soon as I get a chance to do some messing around I will let you guys know how it went. Thanks again hopefully one day I will be able to return the favor.
Ok just double checked and now I need to ask another question. Mobile Odin states that my reactivation lock needs to be turned off but when I go to settings, general, security, there is no option to turn it off. It doesn't even show it in the list. Do I absolutely need to turn it off, would it be somewhere else?
nycemt said:
Ok sorry I took soo long to respond, work has been busy. So I Bought Wifi Tether Router for $2.50 which is still better than 10 extra dollars a month. It works, granted it takes a long time to start up and im not using the stock tether that is included with the phone which would have been great but it gets the job done and I have no complaints. This was one of the main reasons I wanted to root my phone. Anyway I guess when I have some more time to mess with it I will try flashing roms/kernels (I am just soo afraid of hard bricking my phone) but you guys gave some pretty clear instructions so I don't think I'll have a problem. As soon as I get a chance to do some messing around I will let you guys know how it went. Thanks again hopefully one day I will be able to return the favor.
Ok just double checked and now I need to ask another question. Mobile Odin states that my reactivation lock needs to be turned off but when I go to settings, general, security, there is no option to turn it off. It doesn't even show it in the list. Do I absolutely need to turn it off, would it be somewhere else?
Click to expand...
Click to collapse
i don't know. i looked into it and it appears it should be under security, but that was on a s5. maybe your device doesn't have that option.
Do you know what would happen if I backup or flash a rom and the reactivation lock is enabled?
nycemt said:
Do you know what would happen if I backup or flash a rom and the reactivation lock is enabled?
Click to expand...
Click to collapse
i dont know exactly, but through some research it looks like you could run into issues with a custom recovery. i can only assume a rom would be the same.
That really sucks, I'm gonna try and hopefully find a way around it but until then I guess I'm gonna have to wait. Would you happen to know how to check and see if it's activated? (Besides the normal spot in security that it should be)
nycemt said:
That really sucks, I'm gonna try and hopefully find a way around it but until then I guess I'm gonna have to wait. Would you happen to know how to check and see if it's activated? (Besides the normal spot in security that it should be)
Click to expand...
Click to collapse
sorry, i don't know. i had to google search to find the previous information.
What device do you use? Have you enabled this feature (reactivation lock) before? I've made a research that this is an anti-theft feature of galaxy s5 and note 3 which prevents fatory reset of the phone using your samsung acccount when stolen.
I think you don't need to worry about disabling this feature if you never enabled it. I'm using galaxy s3 international version (i9300). And I also don't have this feature. Mobile odin is only reminding you that you should disable reactivation lock (in case you have one) before flashing any rom.
I "guess" reactivation lock enabled will prevent you to format certain partition in your phone since it will be password protected.
I suggest that you use TWRP or CWM when flashing ROMs that are not touchwiz based (Cyanogenmod, AOKP, etc). I only use Mobile odin when flashing recovery and flashing stock firmware. Flashing custom ROMs other than stock, in my opinion, will be safer if you do it in recovery after a backup.
I hope I answered your question.
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
I am in the same boat. Please let me know if you get an unbrick image..
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Chay555 said:
I am in the same boat. Please let me know if you get an unbrick image..
Click to expand...
Click to collapse
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
Good news! I was able to get the phone booted up again. Bad News: Its back on Lollipop firmware (BP1.) So what I did was I used the files from jrkuses working root method 3/4/16 and flashed them through Odin. First I flashed the PB1 unbrick image in his OK3 file, then I flashed the Nk2 kernel also included in the OK3 file, and last I flashed a file called VZW_BPB1_KERNEL_ONLY.tar.md5 also in the folder. Flashing those got me booted back on 5.0 safely.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Chay555 said:
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
Click to expand...
Click to collapse
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
akaplo said:
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
Click to expand...
Click to collapse
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Chay555 said:
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Click to expand...
Click to collapse
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Nandr0idC0nsumer said:
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Click to expand...
Click to collapse
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Chay555 said:
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Click to expand...
Click to collapse
Reset using stock recovery. it usually takes about 20min on the vzw screen
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions. I have hard bricked my phone before I repaired it using win32img creator using an sd card. I never messed with partitions ever again after that.
akaplo said:
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Click to expand...
Click to collapse
stellar0322 said:
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions.
Click to expand...
Click to collapse
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
akaplo said:
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
Click to expand...
Click to collapse
Alright. I'm confused
EDIT: looked through the thread now. That's a hardbrick. Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Nandr0idC0nsumer said:
Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Click to expand...
Click to collapse
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
akaplo said:
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
Click to expand...
Click to collapse
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Nandr0idC0nsumer said:
Reset using stock recovery. it usually takes about 20min on the vzw screen
Click to expand...
Click to collapse
Is good now. Thank You
Chay555 said:
Is good now. Thank You
Click to expand...
Click to collapse
Congrats! You get a cookie.
Nandr0idC0nsumer said:
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Click to expand...
Click to collapse
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
akaplo said:
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
Click to expand...
Click to collapse
I've read up on the Snapdragon 80x boot ROMs, and there appears there is only 1 way to get into qhsusb_bulk mode, which is to have the bootloader corrupted and it is automatically triggered.
If it's not in that mode, it's a brick, go to Verizon and tell them it randomly died
there is nothing that can be done from now. good luck dealing with verizon/samsung and I hope you're still in warranty.
PD1 unbrick image.
https://www.androidfilehost.com/?fid=24562946973631519
Can anyone help? I spent a big chunk of my hard earned money on a refurbed S6 for my daughter, she's had it about a week (she's Pokemon mad btw). The latest update for Pokemon Go came out and now she's blocked from the game as it appears the phone has been rooted. If I'd known, I wouldn't have bought it. Anyway, for the last 2 days my partner and I have been trying to unroot it. We've used various versions of Odin to no avail. I had a lot of trouble finding the right firmware because it looks like the phone was Polish according to the version and CSC numbers, and tbh I'm still not sure if we're trying the right one. Software is 5.1.1. right now. I've tried installing SuperSU but it won't run, it just crashes the phone and forces a reboot. We've tried manually unrooting with a file manager but the su files we need to delete reappear seconds after they're deleted. I'm at the end of my tether, does anyone have any ideas?
You won't be able to unroot it until you flash stock firmware. I don't know if the game checks the knox status.
Give this a go
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Enjoy
Unforunately my partner spent almost all night trying to flash the firmware. According to him it 'nearly' worked, however, I now have a phone stuck in a boot loop. :crying:
Run emergency recovery on Smart switch
ccalixtro said:
Run emergency recovery on Smart switch
Click to expand...
Click to collapse
Do I need to have smart switch installed on the phone for this to work?
amber_1978 said:
Do I need to have smart switch installed on the phone for this to work?
Click to expand...
Click to collapse
No, run it on your pc.
Thanks, I'll give it a go after work.
ccalixtro said:
No, run it on your pc.
Click to expand...
Click to collapse
Smart switch won't work, says it doesn't recognise the device
I think I would give original firmware of your country and odin a try. One of possible ways is to download all needed files from the site of sammobile.
For me this way works every time when I stuck in boot loop. Odin functionates when you are in download mode. Switch off your s6, then start by pressing home-, powerbutton and Volume down at the same time.
Then start Odin on PC, then connect USB and so on.
Greetz JG
amber_1978 said:
Smart switch won't work, says it doesn't recognise the device
Click to expand...
Click to collapse
When you select emergency recovery theres an option where you have to write the device model and the serial number
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
fahad999 said:
Use kies 3 on your computer. When you get it do a "firmware upgrade and installation" it will ask for your serial number which you can get from download mode when pressing the home key. After that kies 3 will ask to boot your phone to recovery but instead boot to download and bow your phone will flash to stock. This method always work!!
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately I've tried Kies already and I can't get it to work at all. I get a message telling me my device is not compatible and the whole thing just stops. I'll give it another go though, no harm in trying. Thanks
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
socal87 said:
@amber_1978, Pokemon Go does not check for root. The only thing it does seem to check for is location spoofing via another app. I'm using it on a rooted, Knox tripped, Xposed installed phone with no issues.
If you want to return the phone back to stock, the best way IMO would be to use Odin to flash a stock image, such as the EPD1 firmware.
Click to expand...
Click to collapse
Really? Did you do the latest update in the game and it still worked ok? This phone has definitley not been used for location spoofing by us and I'm pretty sure there were no apps of that nature on the phone. I downloaded a root checker when everything went wrong the other day, it said the phone was rooted. I'm totally at a loss tbh. Right now it's still in a boot loop. Trying to flash it with Odin as we speak.
Just an update. Tried Smart Switch. Tried the model and serial numbers on the back of the phone case, these weren't recognised so I went to the recovery screen and hit the home button and got a completely different set of numbers. Different IMEI, model number, you name it. I'm assuming this is why Odin won't work, I'm looking for the wrong firmware? I obviously have Frankenstein's phone. No idea what to do now.
Best thing to do is to flash TWRPP and try to flash a custom stock rom through the TWRP recovery which does not have root installed..... If that doesn't work try to find a generic stock firmware for Odin, meaning a firmware that can run in any country..... If all else fails update it to 6.0.1 stock firmware. Try the closest firmwares to your location.
And if you do manage to get to the Samsung logo let the phone sit there for a good 10 minutes even if it reboots....
When I bricked my Samsung I used masiks custom 6.0.1 rom based on stock, but had all the links to bootloaders cscs radios and what not so giv that a shot if you can find it.
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Link to rom that helped me http://forum.xda-developers.com/galaxy-s6/development/masik-marshmallow-1-0-jan-20-2016-t3297961
do you have lucky patcher playstore installed ?
Hey all,
I tried rooting my Galaxy S7 today with Odin 3.11.1 and I thought it all went fine, it said it passed and that it was successful. However when it starts to boot it gets no further than the boot screen which says "Samsung Galaxy S7" and then "Powered by Android" at the bottom. There isn't an unlocked padlock on the screen either which I thought there was meant to be. Any help would be much appreciated and at this point I am more than happy to just go back to stock firmware and forget rooting even exists.
SM-G930F
G930FXXU1DQD7
You can flash stock from updato.com and ODIN 3.12.3 or newer
*Detection* said:
You can flash stock from updato.com and ODIN 3.12.3 or newer
Click to expand...
Click to collapse
Is that guaranteed to fix my problem then and bring it back to stock?
Lethal_Trousers said:
Is that guaranteed to fix my problem then and bring it back to stock?
Click to expand...
Click to collapse
Nothing is a guarantee when you flash devices with custom stuff and break them
But flashing stock is guaranteed to take you back to stock obviously, so long as it flashes successfully (It will not reverse KNOX 0x1 though, good chance you've tripped KNOX already)
Seems you have reservations about flashing stock, but quite happy to try rooting the phone using an outdated ODIN?
Try downloading a stock firmware from sammobile (make sure to find the right model and android version), extract it and then flash it with odin (assuming that you can still enter download mode). File is quite large to download, but Internet Download Manager (IDM) could speed up the process by 4-5 times. As for rooting, I have an S7 myself and I managed to successfully root it using Odin and chainfire's auto root file. However, I was also stuck in your situation the first time I tried and had to factory reset before trying again. Can't remember the cause though.
The easiest way is using samsung smart-switch.
There is a menue "emergency-recovery" or similar.
Follow the instructions and it will automatically download the actual firmware and flash it.
Good luck