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?
I was useing ParadoxII for my phone for 4 months. I was listening to music and one day it stoped working.
The other day it was in infinite bootloop and i got it out! however its back to the same thing....
Here the problem.
phone without sim or Sd i insert battery. it will try to load up quarter way to boot up it will vibrate and turn off.
Then if i try to get into recovery mode (hit threee buttons then let go of power) it may or may not get in... once i am in.. if i dont act fast it will shut off. or if i try to select wipe cache( it might not send the command and shut off)
Ill try to get into download mode. and it will guess what?? shut off and start to vibrate and then vibrate and vibrate
any suggestions?
laserbeam1k said:
I was useing ParadoxII for my phone for 4 months. I was listening to music and one day it stoped working.
The other day it was in infinite bootloop and i got it out! however its back to the same thing....
Here the problem.
phone without sim or Sd i insert battery. it will try to load up quarter way to boot up it will vibrate and turn off.
Then if i try to get into recovery mode (hit threee buttons then let go of power) it may or may not get in... once i am in.. if i dont act fast it will shut off. or if i try to select wipe cache( it might not send the command and shut off)
Ill try to get into download mode. and it will guess what?? shut off and start to vibrate and then vibrate and vibrate
any suggestions?
Click to expand...
Click to collapse
Stuck power button
Sent from my SGH-T989 using xda app-developers app
Stuck power button -_-
you just tried me sir.....
no disrespect but...
that means you think im stupid enough to not know if my power button is broken..... -_-
I FIXED IT YALL!!!! freeking hours upon hours were spent here
ill tell you how i fixed it...
well first i read something about a JIG... a usb jig that makes the phone do directly into download mode....
and i was thinking... hmmm i think iv seen this before automatic download mode...
ah ha! i know i have this thick LG micro usb cable that for some reason if i have low battery it makes it go into download mode..
So... while it was pluged into the wall outlet with ebay battery charger/ usb power outlet and sliped the battery in right quick.
So the cable hooked up to power outlet put in first and quickly the battery is slipped in to make it go into download mode..
however... i only get like 2 seconds before it will shut offf...
so... i turned on odin on my pc and used that cable from my pc. and then hooked up phone to pc via that LG micro usb cable and sliped in the battery fast! then it was in download mode and then i clikced start on the odin ( file preselected) then it will fail and some stuff willbe messed up on the phone and then you can try it again. however this time instead of a download screen its a this phone has problems with recovery and then connect to kies screen.
then use odin while on that screen and proceede.
and boom pass!
however when i put on stock tmobile ics.. my calling wasnt working... WTF!
so i had to put on CWM recover back on the phone via odin..
then i used the backup file i previously made...
Im un bricked!
YES YALL! im unbricked and if this **** bricks again its going on craigs list bc i know it will last a few days before it bricks again
thank you anyways xda.... im not high tech if you cant tell but i can put clues together..
boot loop problem was but no more
Hay had the same darn problem I fixed it by doing hard reset(volume down,menu button, and power button released on first vibration)
Then I went into cwm and went to advanced menu and mounted all but external sd and formatted each one.
Then reflashed stock 2.3.6 GB ROM. Fixed in about 30 min. My phons has not bricked again yay for me
My devices
Cricket zio running bare bones
Samsung galaxy II running rebelrom
T mobile sgs II running stock root 2.3.6
Because I have not found a ROM I like yet!!
Reformatting worked for me
laniclamoore said:
Hay had the same darn problem I fixed it by doing hard reset(volume down,menu button, and power button released on first vibration)
Then I went into cwm and went to advanced menu and mounted all but external sd and formatted each one.
Then reflashed stock 2.3.6 GB ROM. Fixed in about 30 min. My phons has not bricked again yay for me
Click to expand...
Click to collapse
Success!
My bootloop was caused by a bad CWM factory reset or cache wipe with CWM version 6.0.1.9. Nandroid restore from version 6.0.1.9 was of no help as it failed on the MD5 checksum. Odin flashed older CWM, version 5.0.2.6. In CWM version 5.x, reformatting as laniclamoore suggested and restoring nandroid worked for me.
After getting the boot loop solved, I ran DARKSIDE's cache wipe to fix the shutdown hang on pink splash screen 'Goodbye!'. Hang at shutdown was a separate problem caused by CWM version 5.0.2.6.
Lessons learned: CWM sometimes breaks stuff. Good to keep old version of CWM the ones that correspond to the nandroid.
What a pain but it is great to have the Android community to help.
@laniclamoore, Thanks a bunch. I thought my S II was going to be permanently boot looping paperweight.
On T-mobile Samsung Galaxy S II, stock root ICS ROM, 4.0.3.
FIXED: Vibrating Problem on Power Switch onSamsung Galaxy S2 (SGH-T989)
I had the similar problem with my SGH-T989. Searched the web and tried a few feasible solutions, but to no avail. Until NOW: Please follow the YouTube link (https://www.youtube.com/watch?v=pqBgbN8NLjI) which provides a FIX to the Power Switch.
It WORKED for me, hope it works for you too.
Cheers
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
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
Hi my coworker has a sprint galaxy note 2 stock and not rooted. His phone shut down and when he started it back up it was stuck in a bootloop. I tried to flash the stock tar file via Odin and it failed. I don't think usb debugging has been checked in developing options, is their a way to fix this?
Thanks.
Andre
Have you tried using the (incredibly awesome) instruction set and downloads from Billard's (in)famous MC2 build?
http://forum.xda-developers.com/showthread.php?t=2086769
No but I'm going to try it now, I'll keep you posted.
Thanks.
Andre
Now I can't boot into recovery, I flashed twrp and it worked for a while and now it doesn't. I tried to refresh twrp but no luck.
Almost sounds like this could be a hardware issue.
By chance, does he have an extra battery? Or maybe another person in your office (or wherever you are with this) who can let him try their battery as a test? Last summer, my battery ballooned when I took a trip to Colorado up in the mountains (stock Samsung battery) and caused bootloops and just plain crashed my phone. Got a new Duracell from Batteries Plus ($40) and immediately fixed the "problem". You might want to see if he can try another battery next before attempting another software fix.
However, if that doesn't work, have you tried to immediately boot into recovery/download mode after turning on the phone? Then use odin to root/flash ROM/whatever you need?
1) turn off your device (pull battery "just in case" for 10 seconds too)
2) press this button combination: volume up, power button and home button. hold until download mode shows up
3) press volume up to enter the download mode (or volume down to cancel and reboot the device)
I guess that could be the problem. I tried Ballard's MC2 build but it didn't work it put the phone in emergency mode and I had to use kies to get it out of that and now I'm back to a bootloop and stock recovery. I think I'm going to try Philz recovery and flash from there