Develop Bugs

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

I just got this S3 and it wont stop rebooting...

Ok So I just bought this att s3 from Craigslist. As soon as I got home it started restarting , it will reboot like after 10 seconds.
It boots as far as the Samsung logo then restarts. Sometimes it goes all they way to att splash screen then reboots.
What I have tried to fix.
1) boot to recovery whipe data and dalvik, but it won't give me enough time to copleate the command before it restarts.
2) boot to download mode but won't stay on enough time to hook it up to my pc the use odin on it.
3)Booted safe mode and the phone booted up all the way then the power menu came up then restarted.
Im out of ideas Do you think the mother board is messed up?
Plzz help thank you for looking and for your help/...

kipster3001 said:
Ok So I just bought this att s3 from Craigslist. As soon as I got home it started restarting , it will reboot like after 10 seconds.
It boots as far as the Samsung logo then restarts. Sometimes it goes all they way to att splash screen then reboots.
What I have tried to fix.
1) boot to recovery whipe data and dalvik, but it won't give me enough time to copleate the command before it restarts.
2) boot to download mode but won't stay on enough time to hook it up to my pc the use odin on it.
3)Booted safe mode and the phone booted up all the way then the power menu came up then restarted.
Im out of ideas Do you think the mother board is messed up?
Plzz help thank you for looking and for your help/...
Click to expand...
Click to collapse
Did you ask if this was rooted before you got it ? So you got the phone home and had done nothing to it before it started rebooting or did you do something and it start ?
I've heard this happen when someone had a wipe for bad and the recovery gets borked but it could be the power button as well. The hard reboot happens after the power button has been pushed for 10 seconds. This could explain the constant reboots/ Mess around with it and see if that helps. I had this happen on a skyrocket and cappy and the button got "unstuck"

hednik said:
Did you ask if this was rooted before you got it ? So you got the phone home and had done nothing to it before it started rebooting or did you do something and it start ?
I've heard this happen when someone had a wipe for bad and the recovery gets borked but it could be the power button as well. The hard reboot happens after the power button has been pushed for 10 seconds. This could explain the constant reboots/ Mess around with it and see if that helps. I had this happen on a skyrocket and cappy and the button got "unstuck"
Click to expand...
Click to collapse
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . Im gonna have it checked anyway to see if it could be the power button

kipster3001 said:
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . Im gonna have it checked anyway to see if it could be the power button
Click to expand...
Click to collapse
Does it reboots even when plugged/charging?
Did you try another battery?

kipster3001 said:
its not rooted when i manage to get in into download mode its official and the counter is 0 .
the recovery is stock. I did think that It could be the power button stuck but the button clicks . I'm gonna have it checked anyway to see if it could be the power button
Click to expand...
Click to collapse
It's not really a matter of it not clicking physically on the outside but something sticking under that button.
From your initial post to you stated it not always restarting at the exact same point during the boot up. Tend to make me think physical.
If its not rooted and has stock recovery someone might have rooted it before and then tried to put it back stock and borked it somehow.
Have you tried downloading Odin 3.07 and see if it's recognized ?
Did it boot when you bought it ? Please don't tell me you bought it without seeing it boot up first...

hednik said:
Did it boot when you bought it ? Please don't tell me you bought it without seeing it boot up first...
Click to expand...
Click to collapse
+1

Soft brick, but can't access recovery mode

Hey there, so my phone randomly decided to stop working today.
Whenever I put the battery in the phone or plug in the charger, the Samsung screen loads then nothing. This all happens without me pushing the power button btw. Then the power button doesn't work, nor can I access recovery.
Like I mentioned, this all happened very suddenly and unexpectedly. I haven't flashed a rom in awhile so I'm not sure what caused the problem. One tidbit worth mentioning is that my phone would randomly reboot on the rom I've been using, but it wouldn't happen too often.
Any help would be greatly appreciated. Not exactly sure what I should do in this situation. Thanks for reading.

nfsplayer99 said:
Hey there, so my phone randomly decided to stop working today.
Whenever I put the battery in the phone or plug in the charger, the Samsung screen loads then nothing. This all happens without me pushing the power button btw. Then the power button doesn't work, nor can I access recovery.
Like I mentioned, this all happened very suddenly and unexpectedly. I haven't flashed a rom in awhile so I'm not sure what caused the problem. One tidbit worth mentioning is that my phone would randomly reboot on the rom I've been using, but it wouldn't happen too often.
Any help would be greatly appreciated. Not exactly sure what I should do in this situation. Thanks for reading.
Click to expand...
Click to collapse
try to be quicker to access recovery, power off the phone. then press the power, vol up, and home then AS SOON as you see the blue text on the left top side of the samsung logo screen let go of the buttons, it should boot into recovery then wipe data factory reset and reboot.

Andy_nu said:
try to be quicker to access recovery, power off the phone. then press the power, vol up, and home then AS SOON as you see the blue text on the left top side of the samsung logo screen let go of the buttons, it should boot into recovery then wipe data factory reset and reboot.
Click to expand...
Click to collapse
Yeah, I was able to do that once, but then the phone just goes to a black screen and doesn't load anything

nfsplayer99 said:
Yeah, I was able to do that once, but then the phone just goes to a black screen and doesn't load anything
Click to expand...
Click to collapse
flash this recovery attached with odin by booting into download mode via power vol down and home, wipe data factory reset and reboot
http://www.androidfilehost.com/?fid=9390212717148635222 (recovery)
http://www.androidfilehost.com/?fid=9390275921635705049 (odin)
place in pda with only f. reset time and auto reboot checked. it SHOULD only take about 10 seconds to flash. as soon as your phone reboots hold the recovery combo and it should go to it

I can't really access download mode either.
I'll get to the screen that asks if I want to go into download mode, then push the up on the volume rocker, get to the next screen, but then it goes black about a second later.
Thanks for all the help so far though.

nfsplayer99 said:
I can't really access download mode either.
I'll get to the screen that asks if I want to go into download mode, then push the up on the volume rocker, get to the next screen, but then it goes black about a second later.
Thanks for all the help so far though.
Click to expand...
Click to collapse
kinda odd. never had that happen before. ,maybe you could try to reflash the download mode into your phone using this method
http://forum.xda-developers.com/showthread.php?t=2369125(make sure you use a debrick.img http://d-h.st/iEy for att not sprint BTW)
or use a jig. since your phone can still access the boot interface.

nfsplayer99 said:
I can't really access download mode either.
I'll get to the screen that asks if I want to go into download mode, then push the up on the volume rocker, get to the next screen, but then it goes black about a second later.
Thanks for all the help so far though.
Click to expand...
Click to collapse
Have you done this and then connected the USB to see if ODIN will recognize the phone? it's entirely possible that you are getting into download mode, but just can't see it..
It's certainly worth a try.

[Q] issue after rooting Recovery Booting. Set Warranty Bit : Recovery loop

hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t

Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank

same prob
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
Same problem as OP, and I can not get into download mode either. If I do as above, it still goes on booting .

saeidzzz said:
hi, i just decided to root my t mobile note 3 device so the first website was tellin about KINGO 1 step root so i did install KINGO and it said successfully rooted and i clicked finish the phone rebooted and it showed me
Recovery Booting
Set Warranty Bit : Recovery
and this screen keeps looping and i cant even enter recovery mod once the phone turns on it shows me that and it keep looping auto reboot same screen
im not sure if my phone is still alive anymore
any solutions?
thanks.
note 3 t-mobile n900t
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 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 write 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 )

you are a life saver!
Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
I thought I was going to have to factory reset my phone like other forums suggested and lose everything. Thanks to your suggestion I was able to get out of recovery reboot loop. Thank you!

Thanks for your help, you are a lifesaver lol! I saved so much money and time because of you. Have a great day

Frank Westlake said:
Enter download mode (hold [VOLUME-DOWN][HOME][POWER] until buzz, then release [POWER]). At the first download mode screen where it says you can press volume-down to boot normally, press volume-down to boot normally.
Frank
Click to expand...
Click to collapse
But how to enter recovery it still says set warranty bit recovery

i am facing problem with set warranty bit: recovery in samsung J5 model...

samsung j5 500f
i have the same problem when i flash twrp recovery..any solution ????

Ghats normal
Sent from my SM-N900T using XDA-Developers mobile app

My Fix
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine

ulop3z said:
I held down the Down volume key along with the power and spammed the home button until the download screen came on, just keep spamming it while holding down the other keys, it will reboot just keep spamming, then I plugged it in to my computer, opened Odin and re installed the Root and it booted up fine
Click to expand...
Click to collapse
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs

Tmobilefan906 said:
Um. U might wanna flash back to stock. Your phone shouldn't do that. Ur messing up your bootloader. Flash newest firmware via Odin
Sent from my Samsung SM-N900T using XDA Labs
Click to expand...
Click to collapse
The phone is fine now, it was just stuck on the loop and spamming home was the only way out, its fine now I've had no problems and it boots up fine

This happens...
This happens to almost everyone at some point of time. There is no need to worry as you just need to flash recovery like TWRP or CWM. To shed some light on this issue... boot loops mainly happen when you uses the incorrect version of software with your ROM or stock firmware. By using youtube you can look at the videos of your phone model and find the recovery version number needed.
For anyone who has a Note 3 T-Mobile phone who is still stuck! I am willing to make a video to show how to fix this and provide all the firmware/version numbers + links in one bundled location to make it easier.
ALL PHONES ARE VERY specific... ONLY USE THE CORRECT FIRMWARE FOR YOUR MODEL PHONE
Again, if you have a Samsung Note 3 T-Mobile, model number SM-N900T and are still lost. Let me know so I can shot a video and bundle files needed.
---------- Post added at 08:44 AM ---------- Previous post was at 08:38 AM ----------
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc), 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 write 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
Don't be scared by this... just choose the correct versions before blindly trying to install a ROM. Also, only use links from main sources if you dont fell like auditing the code!

Hi guys, sorry for might be late about helping you now years later... But recently I've found something interesting about fixing this issue.
*****
Fix: (100% working in Galaxy Grand Prime SM-G530H)
UPDATED: More detailed info!
# Before flashed Recovery or Root:
1. Root device using Odin or any other rooting known workaround.
2. Backup Recovery (optional), and Kernel using Rashr (available on PlayStore).
3. Flash Custom Recovery (TWRP), using Odin PC software or TWRP android app.
4. Flash backed-up Kernel.img file to Boot partition using TWRP install section.
5. Reboot system (It may take a few time to boot)
# After flashed Recovery or Root: (accidentally or without knowing)
1. Search online and download your exact Phone Stock Kernel.
2. Follow *before flashed* above ↑ from 3rd.
Bonus info:
Even after flashing TWRP, you might be able to Boot device yet, by going to TWRP → Advanced → Reboot system. (It bypass bootlooping to Recovery, while: “Set Warranty Bit : Recovery”).
That's all! Try at your own, then share it!

[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