Related
Bell Galaxy S3 running stock JB rooted
I went to flash to Cyanogenmod 10.1 Nightly, it failed (Error status 7) so I attempted to reboot. Screen went black and stayed black, I left it for a few minutes, nothing happened then tried a battery pull. Now nothing. When I plug into my computer it makes the connect/disconnect chime but nothing else. If I hold down the power for ~10sec my laptop makes the disconnect chime, then when I release the power button it reconnects to my laptop (not sure if that helps any)
Just to further clarify, I cannot get to the download or recovery mod, screen is blank, no led when plugged in either.
Is it hard bricked?
I am looking at mobiletechvideos.com at their JTAG repair service. Is that my only/best option?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
If all you did was try to flash cm10.1 then you are not bricked. You might not be doing the 3 button combo correctly to get back into recovery. Do this...
Pull Battery so power down device and then put it back in.
Hold volume Down, Home, then Power Button.
Release all of them when the 1st screen pops up. It's all about timing here.
That should take you back into recovery so you can just restore the nandroid backup you should've made prior to flashing anything.
No good, the screen is pure black no matter if I just try to power on, vol up + power + home, or vol down + power + home. Black screen.
Pull your battery, leave it out, and then plug it in.. no buttons or anything, it should turn on and see if it gets to the battery charging screen (which should show a lightning bolt only).
If it gets that far, power button and home button until you feel it vibrate, let go and it should boot.. post if it doesn't..
Don't press volume buttons, just home/power combo until it vibes..
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
mooseknuckles1 said:
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
Click to expand...
Click to collapse
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Wiltron said:
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Click to expand...
Click to collapse
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
mooseknuckles1 said:
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
Click to expand...
Click to collapse
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Ya I already had CWM on it. I was trying to flash Cyanogenmod 10.1 nightly (todays release) on to the phone. I had Cyanogen10 on it a while back then switched back to stock firmware. I was curious as to the new JB4.2 so I wanted to try out Cyanogenmod 10.1
Wiltron said:
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Click to expand...
Click to collapse
the OP said in 1st post that he was flashing a rom. never mentioned cwm. the only way to have flashed a rom in the first place and gotten a status 7 would have been in a custom recovery.
reserved
Any chance you flashed an international ROM?
upndwn4par said:
Any chance you flashed an international ROM?
Click to expand...
Click to collapse
exactly.
but what all is actually accomplished before an error message?
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I still have a copy of the zip file on my computer, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Edit:
mooseknuckles1 said:
I still have a copy of the zip file, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
Click to expand...
Click to collapse
Yup, that's the right one.
Could be the SGS3 sudden death???
upndwn4par said:
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Click to expand...
Click to collapse
i hear ya.
i thought thats why the script was set to check the recovery partition to ensure it was a compatible (up-to-date) platform to install from. i dont understand why it would begin installing and then check. but then, i'm no recovery coder
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
mooseknuckles1 said:
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
Click to expand...
Click to collapse
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
xBeerdroiDx said:
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
Click to expand...
Click to collapse
Jig can work for the gs3. They are cheap no matter what. I used them on my cappy.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hi
I have read and tried many of posts here, and other forums, to make my phone work again, but nothing does the trick.
It is about 8 months old, and as of 2 days ago, the top menu (the one you pull down) stopped working, being a windows man, i thought a restart would fix it, but it just made it worse.
Now the phone won´t turn on at all, there is no charge icon when its plugged in, it aint being detected by the computer, the charger gets hot tho, so i suspect it IS charging .. something.
i cant reboot it with the vol up/down + power, the screen is just black.
Tried removing battery while its plugged in and putting it back
Tried removing the battery and turning it on
Tried removing SIM card and turning it on
Tried .. many things
Any suggestions is welcome.
lutcha said:
Hi
I have read and tried many of posts here, and other forums, to make my phone work again, but nothing does the trick.
It is about 8 months old, and as of 2 days ago, the top menu (the one you pull down) stopped working, being a windows man, i thought a restart would fix it, but it just made it worse.
Now the phone won´t turn on at all, there is no charge icon when its plugged in, it aint being detected by the computer, the charger gets hot tho, so i suspect it IS charging .. something.
i cant reboot it with the vol up/down + power, the screen is just black.
Tried removing battery while its plugged in and putting it back
Tried removing the battery and turning it on
Tried removing SIM card and turning it on
Tried .. many things
Any suggestions is welcome.
Click to expand...
Click to collapse
can you boot into download mode? volume down + power?
if not, try omap flash http://forum.xda-developers.com/showthread.php?t=1760787
samersh72 said:
can you boot into download mode? volume down + power?
if not, try omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
No luck im afraid .. just waiting for USB device when clicking the bat file
edit: holy technology batman, it is working .. it couldnt find the phone as the guide said, but desperate as i am i tried turning it on anyway, and here it is, ON
lutcha said:
No luck im afraid .. just waiting for USB device when clicking the bat file
Click to expand...
Click to collapse
did you follow steps of omap? install omap driver?
and what about download mode?
samersh72 said:
did you follow steps of omap? install omap driver?
and what about download mode?
Click to expand...
Click to collapse
Thank you so much, saved me 12.000 baht ... 400 dollar
So a friend of mine was updating ClockWorkMod and within about two reboots his phone would only flash the Samsung logo that pops up when the phone first turns on then nothing would happen (black screen). He reflashed the last version of CM stable (CM 10.1.2 for d2att) and nothing changed.
So I figure, we can just flash back to stock via ODIN but the device will only enter Download Mode for about a split second; it shows the green Android then flashes away to a black screen just like bootup. There was a video taken of the text in the corner, the flash counter was incremented and it said something like "QUALCOMM SECUREBOOT: ENABLED"
To be clear, we can enter CWM recovery just fine with no hiccups but we can't enter Download Mode or boot the device. I've tried booting into each mode with the device plugged into a computer and ADB will only recognize it in recovery mode, not in Download or normal bootup.
Is this a hardware failure? I can't tell and I'm not sure how to proceed. Would a Jig help?
Any help would be appreciated.
EDIT: It has now been discovered and confirmed that a loose power button is the culprit here.
Do you have access to a USB jig to force the phone into download mode?
audit13 said:
Do you have access to a USB jig to force the phone into download mode?
Click to expand...
Click to collapse
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
hakoda said:
We don't but we're skeptical of it working; we fear that once it's in Download Mode and we unplug the Jig so we can plug the phone into the computer, it will turn off.
It does seem like our only option however; do you think we should go ahead and order one?
Click to expand...
Click to collapse
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Larry2999 said:
Since you can get into recovery mode, can you try flashing a stock file via recovery? You can use another device (another phone, SD card reader/writer, card adapter, camera etc) to copy the flashable zip to an SD card, then place the card in your phone and install via recovery. I'll suggest you use the MJ2 (modified 4.3 stock ROM) so you don't lock yourself into the 4.3 bootloader yet. Please check the instructions to see if you'll require the kernel and modem zips as well. If this doesn't work, then you have a hardware problem and not firmware.
http://www.androidfilehost.com/?fid=23196940996968760
Click to expand...
Click to collapse
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
hakoda said:
When I attempt to flash the ROM on CWM, it says something about "script aborted: status 7 (expected 5 arguments, got 3)". Sounds like the way CWM is formatting and mounting the partitions differently than stock recovery.
Click to expand...
Click to collapse
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
audit13 said:
You should load an updated version of CWM. The status 7 error can occur if the ROM is too new for the recovery.
A jig may work but try updating recovery and flashing first.
Click to expand...
Click to collapse
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
hakoda said:
CWM was already updated to its latest; so a TWRP 2.7.0 flashable zip for d2att was executed to see if that would fix the flashing issue but now it won't enter recovery at all
Starting to think the power button is stuck
Click to expand...
Click to collapse
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Larry2999 said:
You could try and see what happens when you remove and replace the battery. Usually, with stuck power button, the phone tries to power on immediately the battery is inserted even when you don't press the power button. Unless, of course, something is broken or dislodged inside. It could indeed be you have a combo hardware/firmware problem. The firmware problem can be easily fixed by flashing a correct and working ROM but you need to be able to get the device into recovery/download first.
Click to expand...
Click to collapse
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
hakoda said:
The insertion of the battery definitely turns on the phone; it's the only way we've been turning the device on and off.
Tapping the front/back of the phone near the power button also seems to randomly wake the device and frankly would explain a lot.
Thanks for the help guys
Click to expand...
Click to collapse
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Larry2999 said:
Sounds like a stuck power button then. Thankfully, this can be routinely fixed at a tech shop or by yourself if you have the right tools and skills for this. Sometimes it doesn't even require replacement of the power button which can be bought cheaply on places like that online auction site.
Click to expand...
Click to collapse
Can confirm that it's a stuck power button; tapping it continuously with an end of a chapstick tube while the phone booted got us all the way into Cyanogenmod; we confirmed that TWRP flashed successfully as well. However, we as soon as we stop tapping it, it goes back to the previous behavior.
We're now looking for some guides online to fix it, seems mechanical if tapping it continuously will keep it unstuck for short amount of time.
Thanks again guys
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
[DELETED]
thebeanogamer said:
So, I may have done a bad. I attempted to install Cyanogen mod on my Vodafone HTC One M8, following the exact instructions on there wiki page, even using their recovery.
Click to expand...
Click to collapse
Cyanogen Recovery? I haven't seen anyone here use it, and wan't even aware it was supported on this device. Did you get the recovery flashed and operational, than tried flashing the ROM? The exact sequence is not clear, from your description.
thebeanogamer said:
It now will not turn on unless I plug it in, when it will do one of two things. Either it will hang on a photo of a battery, or it will hang on that with the red text at the bottom. It always does the latter when plugged into the wall, and mixes it up when plugged into the computer. If it is the latter I cannot turn it off until the battery dies, but in the case of the former it waits a few seconds then powers off. No combination of buttons will turn the device on. I have backups saved, so if I can get into fastboot I can easily fix it.
Click to expand...
Click to collapse
Does the phone reboot if you hold power + vol up for a minute or 2?
[DELETED]
thebeanogamer said:
No unfortunatly to both.
Click to expand...
Click to collapse
I asked a few more questions/clarifications in my previous post. Hard to help, without the proper info.
[DELETED]