Related
Accidentally allowed the battery to drain too low... At first the device would boot up just fine and would get to the OS then shut off. So I downloaded the updated FFF 1.4A.zip flashable bootloader, placed it on the device and was about to install it, in hopes of alleviating this issue, but the device shut off after the file transfer, before I could flash it, and now it will not turn back on.
I'm running this bootloader - http://forum.xda-developers.com/showthread.php?t=1615093 ...
As I said, it won't even turn on (no green light) when I push the button at this point.
When I plug it into the USB cable and/or the wall-charger, the "FIREFIREFIRE Extended Bootloader" screen and the green light just flashes over and over...
Any ideas?
If I could just get it to STOP FLASHING the bootloader screen and get into recovery I have "fff-u-boot_v1.4a.zip" waiting to be flashed...
I had put that file on the device to fix this problem but it shut off on me right after the transfer and it has been flashing the bootloader screen since then...
All I need is to get into recovery!!!!! ARGH!!
I have read from the experts, that you should plug it in, hold the power button down for at least 10 seconds (this makes sure it is off) and let it charge for a couple of hours.
Sent from my Amazon Kindle Fire using xda app-developers app
Yea... I've tried that... However, no matter what I plug it into, USB cable or stock "wall-charger", the bootloader screen just flashes. The power button is unresponsive during this. Holding it down does nothing...
I'm hoping to avoid having to do this - http://forum.xda-developers.com/showthread.php?t=1806620&highlight=battery+dead
But I'm preparing for this last resort as it's becoming increasingly clear that this may be necessary.
Anyone have any other ideas?
Problem solved, new bootloader installed!
For some strange reason the bootloader screen stopped flashing after I decided to try plugging it into the stock wall charger again. It stopped flashing and allowed me to access recovery. I unplugged it and it stayed on long enough for me to install the new bootloader...
All is now good. What is strange however is the bootloader didn't stop the boot process. She booted up right into the OS and stayed on. I plugged it in, navigated to Settings > Battery and it is charging!
VERY WEIRD but very cool!
So for those of you having issues with charging, it's absolutely necessary to have FFF 1.4A bootloader installed! If you cannot get into recovery or the device will not turn on, just keep trying the stock wall charger. Just plug it in and keep plugging it in. Keep on messing with it. Eventually, somehow, it will take enough of a charge to get you into recovery...
When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?
riku-vomoto said:
When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?
Click to expand...
Click to collapse
Don't try to power it on while plugged in. Ain't much else to suggest there. I find doing the button combo for download mode then pressing vol-dn at the warning screen works too. This is the normal it's not a bootloop. The way these charge w/ the power off is strange.
billard412 said:
Don't try to power it on while plugged in. Ain't much else to suggest there. I find doing the button combo for download mode then pressing vol-dn at the warning screen works too. This is the normal it's not a bootloop. The way these charge w/ the power off is strange.
Click to expand...
Click to collapse
Okay sounds good; thought it was just a problem with my phone but guess not lol. Thanks for the quick reply !
riku-vomoto said:
When I plug my phone into my a charger and it is charging my phone gets stuck into a bootloop where I can't turn it off nor turn it on. It wont even go to the Samsung logo, it just is black and keeps turning on/off. Only way I have to get around this is by unplugging, pulling battery, reboot recovery, plug back in, then I can reboot to system. Any ideas on a solution to this?
Click to expand...
Click to collapse
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.
poit said:
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.
Click to expand...
Click to collapse
That's weird as I'm on my 5th s3 since 6-21 and this has been normal behavior on every one regardless of rom. The S2 did the same stupid shiit. Its almost impossible to turn these on while plugged in and shut off.
poit said:
What recovery and rom are you using? This is not a normal behavior. It doesn't happen on my phone using Stock rom/TWRP recovery.
Click to expand...
Click to collapse
I usually use freeg3 from Clark, but I flash about every ROM when they are updated to try it out; I use TWRP to flash them all. My phone is infected with anthrax, but It was before and after it. I even tried flashing the stock .tar from odin :/
When the screen is black, simply hold the power button in until you see the Samsung logo.
Sent from my SPH-L710 using xda premium
I just confirmed again that my phone doesn't do that. With the phone on, I plugged into the charger. Power off, wait until the green battery icon appears. Hold power button, phone boots normally.
I'd guess somewhere along the way you acquired a wonky bootloader. You could probably try just replacing the bootloader, I know there is a way to do that but I'm not sure how. Probably someone else could quote the procedure off the top of their head. If not, I would guess a full odin to stock would fix it also.
My phone does this too. Sometimes it shows a charging battery, sometimes it vibrates, and sometimes I even see the Samsung logo, but it always refuses to turn on while it is plugged up.
My phone doesn't do this. It looks to be a hit or miss on if your phone will do it.
Generating random authentication keys
Or it could have to do with a particular flash that has corrupted the boot loader. People need to be clear what roms they are on, and if they have ever tried to go back to FULL stock through Odin to fix this. Until they have reflashed the Stock Bootloader, there is no way to know what's going on.
Hey guys, I'm not sure if my phone is dead. It was running fine this morning, Task & Ktoonsez' AOKP with Ktoonsez kernel. However, I tried to unlock it a little while ago and it wouldn't go on. It boots to the splash screen, both normally and going into recovery, but it doesn't last long enough to go into recovery or boot normally. I try to boot into download mode and it boots, but the phone turns off after a few seconds.
I tried to flash back to stock in Odin, but the phone doesn't stay in download mode long enough for the flash to finish.
I'm not sure what to do. Any help would be appreciated.
Pretty sure if it was bricked it wouldn't boot into download mode at all. It sounds like it is losing power or something. The only thing I can think of is maybe your battery is bad. Download mode can run off of USB power if you remove the battery after booting into it. Maybe plug your phone in and boot into download mode, then take your battery out before it shuts off and see if it stays on.
Lumixz said:
Pretty sure if it was bricked it wouldn't boot into download mode at all. It sounds like it is losing power or something. The only thing I can think of is maybe your battery is bad. Download mode can run off of USB power if you remove the battery after booting into it. Maybe plug your phone in and boot into download mode, then take your battery out before it shuts off and see if it stays on.
Click to expand...
Click to collapse
No dice. It just did the same thing it's been doing. I went into download, popped the battery, it stayed in download for a few seconds, and then powered off.
Could it be a faulty power button? The phone is constantly vibrating by itself and if the power button was messed up it could be causing the phone to leave download mode.
Sun0fNothing said:
No dice. It just did the same thing it's been doing. I went into download, popped the battery, it stayed in download for a few seconds, and then powered off.
Could it be a faulty power button? The phone is constantly vibrating by itself and if the power button was messed up it could be causing the phone to leave download mode.
Click to expand...
Click to collapse
As far as I can tell pressing or holding the power button in download mode will only restart it, but won't shut it off. Also it takes about 10 seconds. I don't think it's your power button.
Lumixz said:
As far as I can tell pressing or holding the power button in download mode will only restart it, but won't shut it off. Also it takes about 10 seconds. I don't think it's your power button.
Click to expand...
Click to collapse
Ah, okay.
In that case, though, I have no clue what's causing the problem here. At this point the only thing I can do is enter download mode for a few seconds, but I can't get it to be enough time to flash a ROM in Odin.
Sun0fNothing said:
Hey guys, I'm not sure if my phone is dead. It was running fine this morning, Task & Ktoonsez' AOKP with Ktoonsez kernel. However, I tried to unlock it a little while ago and it wouldn't go on. It boots to the splash screen, both normally and going into recovery, but it doesn't last long enough to go into recovery or boot normally. I try to boot into download mode and it boots, but the phone turns off after a few seconds.
I tried to flash back to stock in Odin, but the phone doesn't stay in download mode long enough for the flash to finish.
I'm not sure what to do. Any help would be appreciated.
Click to expand...
Click to collapse
Might be a dumb question... Is your battery charged? I'd plug it in for a while off and see if the battery logo comes up and than try putting it in recovery or download.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Might be a dumb question... Is your battery charged? I'd plug it in for a while off and see if the battery logo comes up and than try putting it in recovery or download.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I tried that too. It's been plugged in for a while and the same thing happens. It just stays in download mode for a few seconds and then turns off. Also, I tried flashing back to stock in Odin but it failed because the phone turned off before the flash could finish. Now the phone says "Firmware upgrade encountered an issue. Please select Recovery mode in Kies and try again."
So it's basically stuck in download mode cause of a corrupted flash. If I could get the phone to stay in download mode, I could flash it back to stock with Odin, but it's not giving me enough time at this point.
I'm running into the same problem currently, I was wondering if you were able to find a solution. Same ROM same Kernel. I've been using my current version of the ROM since October and haven't flashed anything recently, It just died on me last nigth and now I'm experiencing what you are as well. I was able to turn on the phone somehow last night but it stayed on for couple of mins and turned off again. At the time I had 60% charge.
Thanks
Unfortunately not. Sent my phone back to AT&T and they honored the warranty (despite it being very clear that I was rooted and on custom software).
@fly3rr
Sent from the Dank Device
Sun0fNothing said:
Unfortunately not. Sent my phone back to AT&T and they honored the warranty (despite it being very clear that I was rooted and on custom software).
@fly3rr
Sent from the Dank Device
Click to expand...
Click to collapse
Thanks. I got the phone when it launched so it's been over a year hence I'm well over the one year manufacturer warranty. Doubt they'll honor it for me =/.
Bad news, It's not about software, it's a hardware issue.
I had that issue with a Sprint S3,
The power button switch is stuck pressed all the time, you can try to hit it a little and maybe it pops out but the issue is gonna still there.
If you remove and insert the battery does it vibrates and tries to turn on without pressing the power button?
Damian8a said:
Bad news, It's not about software, it's a hardware issue.
I had that issue with a Sprint S3,
The power button switch is stuck pressed all the time, you can try to hit it a little and maybe it pops out but the issue is gonna still there.
If you remove and insert the battery does it vibrates and tries to turn on without pressing the power button?
Click to expand...
Click to collapse
yup I just realized it was the power button issue. I managed to fix the problem[kind of], i kept trying to get into download mode while connected to AC Adapter with official charging cables. And it stayed in download mode long enough for me to go back to stock ROM. I'm just trying to avoid hitting the power button as much as possible because every time I do something goes crazy and phone turns off.
I'm gonna try and go to AT&T store tomorrow to see if they can do anything about this.
Thanks again for your help. I really appreciate it.
You're welcome. Good luck dude :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have the same problem. I've tried to install quickly the twrp. But is not time enough
My problem was the battery. After charge a lot, all thing works fine.
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app
i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty
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