SGH-I747 Won't Boot After 4.3 Update - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I've been looking on multiple other threads for the last few days now but haven't found a fix. I updated my S3 from 4.1.2 to 4.3 through the phone(AT&T recommended update) and it worked for 4 days but was very glitchy. Then it shut off one day with 50% battery and wouldn't turn back on. I tried pulling the battery and turning it on but it would generally fail after it reached the galaxy s3 logo. Can't stay in download mode or recovery mode without it crashing. I sometimes I found that if I leave the battery out for an over 4-5 hours, it can get it to boot and reach my home screen but it soon crashes. Any help would be greatly appreciated since I have been without a phone for about a week. Thank you.

Can you do a factory reset in recovery mode? Not sure if you phone will stay on long enough.

audit13 said:
Can you do a factory reset in recovery mode? Not sure if you phone will stay on long enough.
Click to expand...
Click to collapse
Unfortunately no, the phone doesn't stay on long enough. And I've tried with and without the phone plugged into a charger or my computer but neither really help.

Any warranty left on your phone? If not, you could try flashing a custom recovery in Odin if the phone will stay in download mode, then wipe data, cache from the custom recovery.

audit13 said:
Any warranty left on your phone? If not, you could try flashing a custom recovery in Odin if the phone will stay in download mode, then wipe data, cache from the custom recovery.
Click to expand...
Click to collapse
No I'm pretty sure the warranty is ended since I've had the phone for about a year and 3 months and don't have any insurance through AT&T. How would I go about flashing a custom recovery? Is there a link to a tutorial you could refer me to? Just in case I could get the phone to stay in download mode long enough. Thanks for all your help by the way. I really appreciate it.

Okay. Download the tar version of Philz Touch Recovery from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Install it using Odin by selecting pda and browsing to where you saved the CWM file. Flash it, go into recovery, and wipe.
Good luck. Let me know how it goes.

audit13 said:
Okay. Download the tar version of Philz Touch Recovery from here: url
Install it using Odin by selecting pda and browsing to where you saved the CWM file. Flash it, go into recovery, and wipe.
Good luck. Let me know how it goes.
Click to expand...
Click to collapse
The flash worked and now my phone is staying in recovery. It got into recovery mode and did a factory reset. Now I started up and I started setting up my phone (wifi, google account..) but it crashed multiple times during that setup time. I haven't reached the home screen yet. Occasionally it will boot loop once or twice before reaching the setup again......
So I finally got to the home screen and it crashed (after about 7-8 crashes and reboots). Could it be 4.3 or maybe a hardware problem?

Could be either but let's assume it is an OS issue. Did you flash a custom rom?

audit13 said:
Could be either but let's assume it is an OS issue. Did you flash a custom rom?
Click to expand...
Click to collapse
No I didn't, I don't know of one that I should flash? Recommendations?
Also, my phone was just on for about 8 minutes and was working. I noticed that my power/lock button was extremely touchy and i would barely have to touch(not press it) to lock it. If I press it (like I use to to lock it, it pulls up the power off/options and if I don't do anything about it, it will shut off and restart(boot loop) until i pull the battery and turn it on myself. So I think it might be a problem with the power button being too touchy that it just turns off. Do you know if there is a way to disable the power button?

I run Cyanfox on my brother's S3 and it's pretty stable: http://forum.xda-developers.com/showthread.php?t=2480007
Yes, the power button could be causing the problem. Sounds like the power connection and/or board may be defective.

audit13 said:
I run Cyanfox on my brother's S3 and it's pretty stable:url
Yes, the power button could be causing the problem. Sounds like the power connection and/or board may be defective.
Click to expand...
Click to collapse
Alright I will try to see if I can get that to work. Now the phone is rarely making it to the home screen and if it does, it only stays for at most a minute. Generally it's back to it only getting to the initial Samsung logo.

Is this with the stock ROM?

audit13 said:
Is this with the stock ROM?
Click to expand...
Click to collapse
Yeah it is. All stock.The only change that I made recently was the firmware update to 4.3.

Okay, definitely try Cyanfox to see what happens.

audit13 said:
Okay, definitely try Cyanfox to see what happens.
Click to expand...
Click to collapse
Okay, I'm reading instructions and it says the one of the prerequisites is to have the phone rooted. Is that really the case?

No need to be rooted. You can just flash it in recovery.

audit13 said:
No need to be rooted. You can just flash it in recovery.
Click to expand...
Click to collapse
Alright well it worked right off the bat for about 15 minutes and then crashed. Now it is doing the same sort of thing it was before. It will rarely make it to the home screen but typically just crashes before it gets there. It will crash and then only sometimes turn on when I press the power button. Other times I have to pull the battery and occasionally it will boot loop once or twice.

I think the power button is now the issue.

Related

NEED HELP

So, I have an issue here.
I rooted my wifes phone awhile ago, and recently she has been complaining that she has bad battery life, phone freezing, etc , eyc.
So I figured I would change roms and update CWM.
I relashed this http://forum.xda-developers.com/showthread.php?t=1076967
and everything went fine.
Phone rebooted as if it was back at a default rom, but still rooted.
So I went through the phone setup and got it up and running.
I then put the updated ClockworkMod 3.1.0.1 PURPLE UPGRADE RFS/EXT4 file on my sd card and turned the phone off.
I tried booting the phone into recovery by using the 3 button method and now I am stuck on the black Samsung screen.
I pulled the battery numerous times and I cant get this thing to boot at all.
Someone please help as I am lost here.
Thank you.
Just odin back to stock ec05 and start fresh with one click root + cwm3.1.0.1......
Edit: unless you haven't made a band backup yet then you should try your best to boot up regularly and make a titanium backup
theduce102 said:
Just odin back to stock ec05 and start fresh with one click root + cwm3.1.0.1......
Edit: unless you haven't made a band backup yet then you should try your best to boot up regularly and make a titanium backup
Click to expand...
Click to collapse
Thanks....... Found a thread about using odin, and now have the phone back to default.
I guess I will go ahead and try this all over again.
Thanks for your help.
So, I ran the one click root method found here... http://forum.xda-developers.com/showthread.php?t=1076967
Everything went smooth.
Did all system updates, etc.
Phone was running just fine.
Now when I go to use the 3 button recovery method the phone stays put on the black samsung screen once again!
Cant even boot the phone normally now.
Why is the phone doing this?
This makes no sense at all.
Hmm..... try to flash a pre-rooted rom (like chris41g's ec05 plus rom) and then try to use the 3button method...... if this persists then you should probably stick to using quickboot to get into the recovery.....
Here's the link to the rom ---- http://forum.xda-developers.com/showthread.php?t=1061912
qbking77 knows what he's talking about..... check out his awesome vids on youtube if you ever need a visual aid when flashing =D
JuggZaPoppiN said:
So, I ran the one click root method found here... http://forum.xda-developers.com/showthread.php?t=1076967
Everything went smooth.
Did all system updates, etc.
Phone was running just fine.
Now when I go to use the 3 button recovery method the phone stays put on the black samsung screen once again!
Cant even boot the phone normally now.
Why is the phone doing this?
This makes no sense at all.
Click to expand...
Click to collapse
Yep happens to me as well..... Odin back to stock EC05 again and try a different cable.
If after Odin to stock and rooting you still have problems maybe it is the order you are pushing the buttons. Press and hold camera button first, then add pressing and holding volume down, then add pressing and holding power button, holding all three until the recovery menu comes up.
Hmm..... try to flash a pre-rooted rom (like chris41g's ec05 plus rom) and then try to use the 3button method...... if this persists then you should probably stick to using quickboot to get into the recovery.....
Here's the link to the rom ---- http://forum.xda-developers.com/show....php?t=1061912
Click to expand...
Click to collapse
Is quickboot the answer though.
Because if the phones battery dies, then I might be stuck again seeing it wont boot at all after I power it down.
I did odin it back to default as of now.
Yep happens to me as well..... Odin back to stock EC05 again and try a different cable.
Click to expand...
Click to collapse
Tried with a different cable, and still does the same thing.
If after Odin to stock and rooting you still have problems maybe it is the order you are pushing the buttons. Press and hold camera button first, then add pressing and holding volume down, then add pressing and holding power button, holding all three until the recovery menu comes up.
Click to expand...
Click to collapse
I thought maybe that was the issue as well, but I tried that over and over again with no luck at all.
Do you guys think maybe its related to the latest one click cwm method?

S3 won't boot, load CWM, go into download mode...

Alright, so I have an i-747 (AT&T GS3) running AOKP Jellybean (8.28 build) with the KT747 kernel. I just tried to install Chainfire 3D using the automated installer, and when the phone rebooted, it stuck at the Samsung Galaxy S3 logo until I pulled battery. So I tried rebooting into CWM - same problem. And again with download mode. Even after pulling the battery for a good 5 minutes, nothing works. Am I bricked, or is there some fix for this?
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
g2tegg said:
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I made a nandroid just this afternoon, but I can't actually boot into CWM at all. As in, I turn on the phone (power+home+volume up), it gets to the Galaxy S3 logo and just hangs there. If I could get into CWM (or download mode) this would be about a 10 minute fix, but I'm kind of out of luck here.
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
HELP I have the same issue
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
Hi, sorry to say but sounds like its bricked
Thanks
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
I doubt it's bricked if he got it into download mode. I'm sure he's flashed it and even got his wallpaper back up by now. Please let us know of you've managed to solve this or not MrPhantom.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
delete post please
Curious?
I know its technically "Solved" but does anyone have any idea why this is happening? I have a Verizon GS3 and it's happening to me. I try to boot and it vibrates once and doesn't turn on. Recovery does the same thing. But going into Download mode works. Odin back to stock as we speak but I'm just curious what went wrong. I just did a clean install of a rom, set it all up (working at the time), set it down for the night and woke up to it like this.
rrrs444230 said:
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
Click to expand...
Click to collapse
Same thing happned to me but your not bricked. You can get into bolth download and boot mode easy
Here is how you do it.
RECOVERY MODE
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
[edit]Download Mode
Save that somewhere. Make sure do it right. I got stuck also and thought I couldn't get into recovery but I had to do it right (it hit recovery mode first try) I have learned that most people do it slightly wrong. Make sure follow directions
Download mode
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
To get out of Download Mode, simply press and hold the power button until the phone restarts
if helps hit thanks.
Just save that to a text file somewhere
I have also soft bricked when I deleted my rom once on accident. I dunno how I did it but I would get stuck at the TWRP screen. It wouldn't go to download or anything however when I plugged it into odin it saw it .... I even had a soft brick when screen went black from a bad boot animation and same thing.. and I had one bad soft brick where it took about 100 trys to get it into download mode (black screen) but odin detected it. I spent like 4 hours working on it.
I think
1. People don't follow directions correct (they do it a little wrong) which is enough if your phones messed up for it not to work.
when your phones normal it can get into recovery or download easy but when its sick you got to do it perfect.
2. I think something wrong with the phones (my s2 never had any issues in 2 years of owning it) S3 has tons of issues from usb, to bluetooth, to these soft bricks I have had)
3. Roms play a big part
4. I also think the way storage works in this new phone causes lots issues I dunno why just what I think
anyway Like I said now when I have a isssue I open text and read it and make sure I do it right and 95 percent of the time it was my fault I wasn't doing it right. K just my thoughts
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
phatchef1 said:
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
Click to expand...
Click to collapse
That's most likely cause you're not in the right section..: http://forum.xda-developers.com/forumdisplay.php?f=1708

Stuck/reboot in download mode

Hey guys, ran into a problem and was wondering if anyone knew a fix.
My s4 will only reboot in download mode. If I do a battery pull and then put the Battery back in, it will automatically turn on in download mode. I've tried with both batteries and same thing.
Only way for me to get around this is to pull the battery, hold button combo for download mode (vol down + power) then reinsert the battery. Once the warning screen comes on, hit cancel, and it will boot normally. But if I go to the menu to reboot, it will only go to download mode and I'll have to do a battery pull again.
No idea why this is happening. It started happening when my Battery was low. So I turned it off to switch out to a new battery. Once the new battery was inserted, it auto started in download mode. Wtf!
I'm running rooted stock. I had twrp installed through goo manager (i think) but never flashed a rom. That was months ago and I never ran into a problem until now.
Any fixes for this? Unfortunately I'm halfway around the world on vacation and won't have access to a computer for awhile. Is my only option using ODIN to flash the stock rom? I hope there's another way around this.... Thanks in advance guys
Lick My Toes said:
Hey guys, ran into a problem and was wondering if anyone knew a fix.
My s4 will only reboot in download mode. If I do a battery pull and then put the Battery back in, it will automatically turn on in download mode. I've tried with both batteries and same thing.
Only way for me to get around this is to pull the battery, hold button combo for download mode (vol down + power) then reinsert the battery. Once the warning screen comes on, hit cancel, and it will boot normally. But if I go to the menu to reboot, it will only go to download mode and I'll have to do a battery pull again.
No idea why this is happening. It started happening when my Battery was low. So I turned it off to switch out to a new battery. Once the new battery was inserted, it auto started in download mode. Wtf!
I'm running rooted stock. I had twrp installed through goo manager (i think) but never flashed a rom. That was months ago and I never ran into a problem until now.
Any fixes for this? Unfortunately I'm halfway around the world on vacation and won't have access to a computer for awhile. Is my only option using ODIN to flash the stock rom? I hope there's another way around this.... Thanks in advance guys
Click to expand...
Click to collapse
That seems like the only option you have will be to Odin back to stock. It looks like you have tried to get it to boot right by what you have said.
Mobile Odin should work. Not sure because I never have used it. Maybe someone that has will give you a heads up on it.
My S4 Is Insane
Deviant Team Member
The Sickness said:
That seems like the only option you have will be to Odin back to stock. It looks like you have tried to get it to boot right by what you have said.
Mobile Odin should work. Not sure because I never have used it. Maybe someone that has will give you a heads up on it.
My S4 Is Insane
Deviant Team Member
Click to expand...
Click to collapse
I've used mobile Odin to go back to stock but it only worked on MDL and not mk2.
Sent from my SGH-M919 using xda app-developers app
Can you guys by any chance explain what went wrong? Bad bootloader?
Anyone?
That's not a common problem. I've never even HEARD of anything like that. It sounds like a corruption somewhere. But where? I don't know. Maybe no one does. I'm sorry
Tapatalk Pro 4 - GS4(M919)
?dbombRom is dbestRom?
Lick My Toes said:
Can you guys by any chance explain what went wrong? Bad bootloader?
Click to expand...
Click to collapse
I would start by downloading and flashing a custom ROM. Download the one you like and put it on your sd. From what I understand in your post you can only reboot to download from the power menu. If so you can probably use a terminal from the play store and grant it permissions. Type SU and give it permissions then type reboot recovery. You can also reboot into recovery from Goo manager. Once you achieve recovery make sure you have your ROM in your SD then do a full wipe by going to factory reset and choosing advance wipe. Select ONLY data, cache, dalvik cache and system. DO NOT wipe anything else or you will erase your OS. Once you wipe you can flash your ROM and let it sit for 10 minutes. Now you can try to reboot and see what happens. If it doesn't work then you most likely have a faulty device so the best thing to do is go back to stock, reset your counter and return your device. I hope you get it worked out! Good luck.
Sent from my SGH-M919 using xda app-developers app
Well I used ODIN and went back to stock, it still only reboots into download mode. I flashed a ROM before doing that, problem still there. After using Odin, I can no longer use goo manager to flash a custom recovery. I will hitmenu then "install openrecoveryscript" it will download.... Then nothing. I will wait the 10 seconds then it goes back to the goo manager screen. I tried getting root and that also no longer works. Can also no longer boot into stock recovery.(vol up+home+power) it just boots into download mode. Am I screwed here? No other option than to send back to T-Mobile? I want to avoid that if at all possible. Any other options I may have?
Sent from my Nexus 7 using xda app-developers app

[Q] T-Mobile Note 3 stuck in a auto-restarting, recovery bootloop

Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks

OMG Please help! Bootloop, can't get into recovery but able to get into download mode

I have a SM-G925T and it started boot loop today. I tried to get into recovery mode by holding Power+VOL UP+Home but that does nothing. When I tried to go into download mode by holding Power+VOL DOWN+Home, it works fine.
Symptom:
Phone boot loops displaying only the very first Samsung screen with Galaxy s6 edge (no samsung boot animation). Once this very first logo screen comes on, the screen goes black and loops again. Even if I plug the OEM Samsung USB charging cable, screen does not show the battery charging screen, just the same Samsung Galaxy s6 edge screen.
I have already tried the following:
1. Flash stock rom using ODIN, flashed successfully, still boot loop
2. Holding Power+Vol DOWN to reset, still boot loop
3. Flash stock rom using ODIN again, flashed successfully, still boot loop
4. Let battery drain, waited 3 hours for screen to boot loop and battery died, plugged back USB charging cable back, still boot loop
5. Flick the power button many times to loosen any dirt, still boot loop
6. Hold the power button for 1 minute, 2 minute, and 3 minute, still boot loop
Please help, any advice very appreciated!
Hm, I had this 2 month ago with a S4...
Same thing, I go to my provider he checked the Handy and said I have a defect on my Mainboard... He use dos tools for Handy analysis... I flash stock with Odin, too... Success but no boot...
CarHDRom V.27.3 by Carotix S6edge
nyknight77 said:
I have a SM-G925T and it started boot loop today. I tried to get into recovery mode by holding Power+VOL UP+Home but that does nothing. When I tried to go into download mode by holding Power+VOL DOWN+Home, it works fine.
Symptom:
Phone boot loops displaying only the very first Samsung screen with Galaxy s6 edge (no samsung boot animation). Once this very first logo screen comes on, the screen goes black and loops again. Even if I plug the OEM Samsung USB charging cable, screen does not show the battery charging screen, just the same Samsung Galaxy s6 edge screen.
I have already tried the following:
1. Flash stock rom using ODIN, flashed successfully, still boot loop
2. Holding Power+Vol DOWN to reset, still boot loop
3. Flash stock rom using ODIN again, flashed successfully, still boot loop
4. Let battery drain, waited 3 hours for screen to boot loop and battery died, plugged back USB charging cable back, still boot loop
5. Flick the power button many times to loosen any dirt, still boot loop
6. Hold the power button for 1 minute, 2 minute, and 3 minute, still boot loop
Please help, any advice very appreciated!
Click to expand...
Click to collapse
Hold the button combo pwr, vol down and home as if you want to go into download mode, but try to time it that immediately before the download mode screen comes on, use the Vol up, home and pwr combo and keep holding it down, till it goes into recovery. You have to time it so that right begore the download screen lites up you shift to the recovery mode 3 button combo and hold it till it goes into recovery. This works for me and how I do it all the time whether using stock recovery or TWRP.
Docmjldds said:
Hold the button combo pwr, vol down and home as if you want to go into download mode, but try to time it that immediately before the download mode screen comes on, use the Vol up, home and pwr combo and keep holding it down, till it goes into recovery. You have to time it so that right begore the download screen lites up you shift to the recovery mode 3 button combo and hold it till it goes into recovery. This works for me and how I do it all the time whether using stock recovery or TWRP.
Click to expand...
Click to collapse
Thanks for your suggestion Docmjldds but that didn't work either. I think I timed it within 0.5 second of the download mode screen. I always tried cancelling out of download mode and quickly holding the combo vol up, home, and pwr immediately after it and it that did not work either.
nyknight77 said:
Thanks for your suggestion Docmjldds but that didn't work either. I think I timed it within 0.5 second of the download mode screen. I always tried cancelling out of download mode and quickly holding the combo vol up, home, and pwr immediately after it and it that did not work either.
Click to expand...
Click to collapse
What version Odin?
What version stock ROM?
What version Recovery?
Have you tried to simply install latest TWRP 3.1.0 "twrp-3.1.0-0-zeroltetmo.img.tar"
nyknight77 said:
I have a SM-G925T and it started boot loop today. I tried to get into recovery mode by holding Power+VOL UP+Home but that does nothing. When I tried to go into download mode by holding Power+VOL DOWN+Home, it works fine.
Symptom:
Phone boot loops displaying only the very first Samsung screen with Galaxy s6 edge (no samsung boot animation). Once this very first logo screen comes on, the screen goes black and loops again. Even if I plug the OEM Samsung USB charging cable, screen does not show the battery charging screen, just the same Samsung Galaxy s6 edge screen.
I have already tried the following:
1. Flash stock rom using ODIN, flashed successfully, still boot loop
2. Holding Power+Vol DOWN to reset, still boot loop
3. Flash stock rom using ODIN again, flashed successfully, still boot loop
4. Let battery drain, waited 3 hours for screen to boot loop and battery died, plugged back USB charging cable back, still boot loop
5. Flick the power button many times to loosen any dirt, still boot loop
6. Hold the power button for 1 minute, 2 minute, and 3 minute, still boot loop
Please help, any advice very appreciated!
Click to expand...
Click to collapse
I have the solution for you my friend. Flash TWRP using oding (in download mode), then from TWRP install or flash this rom(for this you need to download the rom, connect your phone to the pc and while you have TWRP open in your screen put the file of the rom in the phone)
Rom right here:
https://forum.xda-developers.com/ga...ied-development/noble-nougat-rom-1-0-t3565293
This works because this rom comes with its own bootloader and kernel.
maxter55 said:
I have the solution for you my friend. Flash TWRP using oding (in download mode), then from TWRP install or flash this rom(for this you need to download the rom, connect your phone to the pc and while you have TWRP open in your screen put the file of the rom in the phone)
Rom right here:
https://forum.xda-developers.com/ga...ied-development/noble-nougat-rom-1-0-t3565293
This works because this rom comes with its own bootloader and kernel.
Click to expand...
Click to collapse
Really appreciate your help here. Would flashing TWRP with odin trip knox? I'm afraid to flash anything not stock rom related.
Docmjldds said:
What version Odin?
What version stock ROM?
What version Recovery?
Have you tried to simply install latest TWRP 3.1.0 "twrp-3.1.0-0-zeroltetmo.img.tar"
Click to expand...
Click to collapse
Really appreciate your help also.
I'm using Odin v3.11.1
Tried both stock ROM version
- G925TUVS5EQA2_G925TTMB5EQA2_TMB
- G925TUVU5EQC2_G925TTMB5EQC2_TMB
Stock recovery was flashed successfully as part of ROM above
I've not tried installing TWRP, could you please point me to where I can find it and how to install it? Also, would installing it trip up my knox?
I also flashed recovery.img by itself by extracting that from the ROM and converting it to recovery.tar.md5 using tar-Tool and successfully flashed recovery only but still no difference.
nyknight77 said:
Really appreciate your help also.
I'm using Odin v3.11.1
Tried both stock ROM version
- G925TUVS5EQA2_G925TTMB5EQA2_TMB
- G925TUVU5EQC2_G925TTMB5EQC2_TMB
Stock recovery was flashed successfully as part of ROM above
I've not tried installing TWRP, could you please point me to where I can find it and how to install it? Also, would installing it trip up my knox?
I also flashed recovery.img by itself by extracting that from the ROM and converting it to recovery.tar.md5 using tar-Tool and successfully flashed recovery only but still no difference.
Click to expand...
Click to collapse
Flashing TWRP WILL trip knox. So, if that's a concern to you, then not much more I can tell you about that. BUT.....3.12.3 is latest ODIN. I would use THAT. Then try flashing complete stock firmware from download mode. QC2 being the last. Here is latest ODIN I attached.
nyknight77 said:
Really appreciate your help also.
I'm using Odin v3.11.1
Tried both stock ROM version
- G925TUVS5EQA2_G925TTMB5EQA2_TMB
- G925TUVU5EQC2_G925TTMB5EQC2_TMB
Stock recovery was flashed successfully as part of ROM above
I've not tried installing TWRP, could you please point me to where I can find it and how to install it? Also, would installing it trip up my knox?
I also flashed recovery.img by itself by extracting that from the ROM and converting it to recovery.tar.md5 using tar-Tool and successfully flashed recovery only but still no difference.
Click to expand...
Click to collapse
PS: Have you tried turning phone off. Then power on and then immediately hold the vol up home pwr buttons combo. That should also get you into recovery mode. But that said, I would still try my last.
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
maxter55 said:
I have the solution for you my friend. Flash TWRP using oding (in download mode), then from TWRP install or flash this rom(for this you need to download the rom, connect your phone to the pc and while you have TWRP open in your screen put the file of the rom in the phone)
Rom right here:
https://forum.xda-developers.com/ga...ied-development/noble-nougat-rom-1-0-t3565293
This works because this rom comes with its own bootloader and kernel.
Click to expand...
Click to collapse
He wants to keep stock. NOT a good idea
Docmjldds said:
Flashing TWRP WILL trip knox. So, if that's a concern to you, then not much more I can tell you about that. BUT.....3.12.3 is latest ODIN. I would use THAT. Then try flashing complete stock firmware from download mode. QC2 being the last. Here is latest ODIN I attached.
Click to expand...
Click to collapse
I used the ODIN 3.12.3 that you posted and flashed QC2 again (Passed/succeeded). Still boot loops.
I can easily get into download mode but not recovery mode. I don't know of a way to power off, just reset by holding power button or (power button and vol down). I just realized how ridiculous this sounds but is there any way to actually power off the phone without loading android and holding power button, and selecting power off? As far as I know, there's only soft reset or hard reset.
I'm pretty sure my hardware buttons work fine since I need to hold power button, vol down, and home at the same time to enter download mode perfectly. Then I have to press volume up button to enter download mode. So all the buttons that's needed to enter recovery mode (power, volume down, and home) works.
Wonder if bad battery can be be the cause? I don't get any charging indicator (screen with battery animation) when I plug phone to USB charger. Seems to be able to hold a charge but not that long, no way for me to check battery percentage though.
nyknight77 said:
Really appreciate your help also.
I'm using Odin v3.11.1
Tried both stock ROM version
- G925TUVS5EQA2_G925TTMB5EQA2_TMB
- G925TUVU5EQC2_G925TTMB5EQC2_TMB
Stock recovery was flashed successfully as part of ROM above
I've not tried installing TWRP, could you please point me to where I can find it and how to install it? Also, would installing it trip up my knox?
I also flashed recovery.img by itself by extracting that from the ROM and converting it to recovery.tar.md5 using tar-Tool and successfully flashed recovery only but still no difference.
Click to expand...
Click to collapse
It's your only option right now. I was where you were and I have the same phone 925T. I flashed the rom I told you about then I flashed the stock nougat rom that just came out 2 days ago. I'm running the stock nougat and I'm happy at the moment. Battery and performance are great. I tried flashing all of the stock roms using ODIN and nothing would work but flashing that rom I linked you before worked and then I was able to go back to stock. Trip Knox sure but you will have a working phone again.
The reason why I went back to stock is because I need WIFI calling.
---------- Post added at 05:56 AM ---------- Previous post was at 05:46 AM ----------
nyknight77 said:
I used the ODIN 3.12.3 that you posted and flashed QC2 again (Passed/succeeded). Still boot loops.
I can easily get into download mode but not recovery mode. I don't know of a way to power off, just reset by holding power button or (power button and vol down). I just realized how ridiculous this sounds but is there any way to actually power off the phone without loading android and holding power button, and selecting power off? As far as I know, there's only soft reset or hard reset.
I'm pretty sure my hardware buttons work fine since I need to hold power button, vol down, and home at the same time to enter download mode perfectly. Then I have to press volume up button to enter download mode. So all the buttons that's needed to enter recovery mode (power, volume down, and home) works.
Wonder if bad battery can be be the cause? I don't get any charging indicator (screen with battery animation) when I plug phone to USB charger. Seems to be able to hold a charge but not that long, no way for me to check battery percentage though.
Click to expand...
Click to collapse
Before doing all this, if you don't want to void your warranty.
1-Download the stock NOUGAT, flash it using odin and then if it lets you go in recovery mode, factory reset your phone then try to boot. Give it 5-10 minutes to make sure it doesn't actually boot. I know the first boot takes a while so you will be stuck at the t-mobile logo. If after 10 minutes doesn't go on then try number 2.
2-Having the phone in download mode use the software smart switch.
Follow the instructions in this video.
https://www.youtube.com/watch?v=Lwz6bF-aqk4&t=30s
If none of that works, either use your warranty or
Follow the instructions to install TWRP.
https://forum.xda-developers.com/ga...ecovery-official-twrp-galaxy-s6-edge-t3354508
maxter55 said:
It's your only option right now. I was where you were and I have the same phone 925T. I flashed the rom I told you about then I flashed the stock nougat rom that just came out 2 days ago. I'm running the stock nougat and I'm happy at the moment. Battery and performance are great. I tried flashing all of the stock roms using ODIN and nothing would work but flashing that rom I linked you before worked and then I was able to go back to stock. Trip Knox sure but you will have a working phone again.
The reason why I went back to stock is because I need WIFI calling.
---------- Post added at 05:56 AM ---------- Previous post was at 05:46 AM ----------
Before doing all this, if you don't want to void your warranty.
1-Download the stock NOUGAT, flash it using odin and then if it lets you go in recovery mode, factory reset your phone then try to boot. Give it 5-10 minutes to make sure it doesn't actually boot. I know the first boot takes a while so you will be stuck at the t-mobile logo. If after 10 minutes doesn't go on then try number 2.
2-Having the phone in download mode use the software smart switch.
Follow the instructions in this video.
https://www.youtube.com/watch?v=Lwz6bF-aqk4&t=30s
If none of that works, either use your warranty or
Follow the instructions to install TWRP.
https://forum.xda-developers.com/ga...ecovery-official-twrp-galaxy-s6-edge-t3354508
Click to expand...
Click to collapse
So I just flashed the latest nougat stock firmware with ODIN. Flashed passed/succeeded. No difference, still boot loop Still cannot get into recovery mode but can get into download mode fine like before.
My phone is out of warranty so I'm just gonna buy a replacement battery off ebay and see if that makes any difference. Hope someone has other ideas. I'll use TWRP as a last resort. Maybe that will work but I don't know how not being able to get into stock recovery would be fixed by installing TWRP custom recovery. I suspect I would not be able to get into TWRP recovery either.
nyknight77 said:
So I just flashed the latest nougat stock firmware with ODIN. Flashed passed/succeeded. No difference, still boot loop Still cannot get into recovery mode but can get into download mode fine like before.
My phone is out of warranty so I'm just gonna buy a replacement battery off ebay and see if that makes any difference. Hope someone has other ideas. I'll use TWRP as a last resort. Maybe that will work but I don't know how not being able to get into stock recovery would be fixed by installing TWRP custom recovery. I suspect I would not be able to get into TWRP recovery either.
Click to expand...
Click to collapse
Why are you so concerned about tripping knox, since you are out of warranty anyways. And BTW it's a myth that a rooted phone loses warranty. I have had plenty of my phones covered under warranty and they were ALL rooted. With TWRP installed, you can use the advanced wipe actions to basically factory reset and load either Nougat or MM stock. I am rooted using stock just released Android 7 for TMobile firmware. Odin Firmware. Odin TWRP. Then install anything you like. Yes...knox tripped. Yes, you will lose Samsung Pay. For me not a big deal. Otherwise just fine. The warranty comany has to prove that your act of rooting caused the issue the phone has. Samsung will tell people that phone warranty is voind if rooted. But it's ONLY a line they are told to state. Again, I have used Samsung warranty direct...NOT TMobile and obtained free warranty service and my phones were rooted.
Docmjldds said:
Why are you so concerned about tripping knox, since you are out of warranty anyways. And BTW it's a myth that a rooted phone loses warranty. I have had plenty of my phones covered under warranty and they were ALL rooted. With TWRP installed, you can use the advanced wipe actions to basically factory reset and load either Nougat or MM stock. I am rooted using stock just released Android 7 for TMobile firmware. Odin Firmware. Odin TWRP. Then install anything you like. Yes...knox tripped. Yes, you will lose Samsung Pay. For me not a big deal. Otherwise just fine. The warranty comany has to prove that your act of rooting caused the issue the phone has. Samsung will tell people that phone warranty is voind if rooted. But it's ONLY a line they are told to state. Again, I have used Samsung warranty direct...NOT TMobile and obtained free warranty service and my phones were rooted.
Click to expand...
Click to collapse
The biggest concern about tripping knox for me is that I lose Samsung Pay. It's actually the most useful thing I have on the phone. I can do pretty much every thing on my old phones that I need but it doesn't have samsung pay. I understand it's useless for most people, but for me it's the most important feature.
Do you think i would still have the same problem getting into recovery even if I flashed TWRP? Right now I can't even load stock recovery.
nyknight77 said:
The biggest concern about tripping knox for me is that I lose Samsung Pay. It's actually the most useful thing I have on the phone. I can do pretty much every thing on my old phones that I need but it doesn't have samsung pay. I understand it's useless for most people, but for me it's the most important feature.
Do you think I would still have the same problem getting into recovery even if I flashed TWRP? Right now I can't even load stock recovery.
Click to expand...
Click to collapse
I really have no idea why you are having this issue. The one time my phone was so screwed up was I could ONLY fix by doing a complete factory reset including internal memory and that was via TWRP. Installing TWRP WILL kill Knox, therefore no more Samsung Pay...period. Have you tried smart switch out of curiosity?
Docmjldds said:
I really have no idea why you are having this issue. The one time my phone was so screwed up was I could ONLY fix by doing a complete factory reset including internal memory and that was via TWRP. Installing TWRP WILL kill Knox, therefore no more Samsung Pay...period. Have you tried smart switch out of curiosity?
Click to expand...
Click to collapse
I think my problem is worst than what you had before because I cannot even get into recovery mode not just a normal boot loop. This issue is boot loop and not being able to get into recovery mode.
I have not used smart switch yet. I was going to do an emergency software recovery but that would basically just wipe all internal memory and flash the stock rom. I thought I could save some of my data by just flashing stock rom with ODIN, which flashed perfectly every time but still boot loops.
nyknight77 said:
I think my problem is worst than what you had before because I cannot even get into recovery mode not just a normal boot loop. This issue is boot loop and not being able to get into recovery mode.
I have not used smart switch yet. I was going to do an emergency software recovery but that would basically just wipe all internal memory and flash the stock rom. I thought I could save some of my data by just flashing stock rom with ODIN, which flashed perfectly every time but still boot loops.
Click to expand...
Click to collapse
The only thing I can think of is that your setup is so corrupted you basically have no choice here. It's kind of the old adage about knowing it's important to occasionally back up the internal data, but just never get to it. I'm kind of paranoid to every now and then make sure I have copies of stuff around. I know it's zero solace for you, but without getting into recovery mode, there is no way to get to the Internal stuff that I know of. I'm assuming you never used smartswitch to backup or just use a computer to copy paste Internal stuff to a folder for saving.
HMMMM...Password:
ZiDroid.com
Try this stock Recovery. I found a post I made almost two years ago with a link to this file. Use the password to open the file and try ODIN again
nyknight77 said:
I think my problem is worst than what you had before because I cannot even get into recovery mode not just a normal boot loop. This issue is boot loop and not being able to get into recovery mode.
I have not used smart switch yet. I was going to do an emergency software recovery but that would basically just wipe all internal memory and flash the stock rom. I thought I could save some of my data by just flashing stock rom with ODIN, which flashed perfectly every time but still boot loops.
Click to expand...
Click to collapse
I realize I'm kinda grasping at straws here short of a complete nuke of your setup....but sometimes you have to bite the bullet so to speak
Docmjldds said:
I realize I'm kinda grasping at straws here short of a complete nuke of your setup....but sometimes you have to bite the bullet so to speak
Click to expand...
Click to collapse
Really appreciate your help. I'm starting to think more that it's a bad battery now. Hope that's just it instead of the main board.
I left phone on charge for a few hours (constantly boot looping the whole time). I'm able to power off the phone by holding Power button and Volume down for 10 seconds. Screen is completely off, no boot looping.
Step1: When try to simply turn phone on by holding power button for three seconds, the first samsung galaxy s6 edge logo screen pops up but then goes away and phone looks to be off. Like it's trying to get power from the battery but can't.
Step2: If I keep holding the power button, that first logo screen would turn on and off as if it's a boot loop. If I let go, then phone is off again.
Step3: If I go into download mode and select Cancel (restart phone), it goes into boot loop with only first logo screen again. It loops until I hard reset by holding power button and volume down again for 10 seconds. Then phone is off. Same thing repeats if I go back to Step1 again.

Categories

Resources