Phone keeps rebooting, cannot get into download mode - AT&T Samsung Galaxy Note I717

I had the phone on the newest PAC-MAN nightly, and I rebooted to my recovery (CWM 6.0.4.4) and flashed another recovery (TWRP 2.7.1) However, after I flashed it and went to reboot to recovery, it would not boot, simply vibrate until the first Samsung sign flashes, and then reboots. I cannot reboot into recovery, and trying to put it into download mode just does the same thing. Is there any way to someone force it into download mode so I can flash stock or anything? Thanks so much

I believe it's Volume up + Power to get it straight to download mode.

Your power button is stuck so it keeps resetting. Try flicking the back of your phone by the power button with your finger.

440bro said:
Your power button is stuck so it keeps resetting. Try flicking the back of your phone by the power button with your finger.
Click to expand...
Click to collapse
That did it. I'm surprised, I've never had this problem with this phone, thanks so much!

MadnessG said:
That did it. I'm surprised, I've never had this problem with this phone, thanks so much!
Click to expand...
Click to collapse
You're one of hundreds plagued with this problem. We should start a club!
Glad you're up and running again.

Related

[Q] Help please. Phone stuck in bootloop can't get into recovery

So here's the gist of it all...
I have an HTC Evo 4G LTE (which is why I'm in this forum) that has been unlocked and rooted using the HTC-Method and is still S-ON. I am using TWRP and my rom is the MeanRom ICS version 4.9. I didn't change any of the settings (i.e. I didn't change any of the values that would affect performance). My phone has been working fine up until this point which is why I am currently asking you all for your help. Last I checked everything was working fine until my phone tried to connect to multiple WiFi access points at the same time and the system crashed I'm guessing and is currently looping.
I have tried a hard reset by holding down the power button til the soft keys blinked and the phone turned off, but it boots itself back up and goes into a loop again. It won't stay turned off and won't completely turn off. I have tried holding the power and up button to get into recovery and it doesn't do anything. I've tried holding the up button as it goes into the next loop to no avail.
For those familiar with MeanRom, it goes past the HTC screen that says this rom is for development purposes etc...then shows the little blue, roaring android, and finally gets the the MeanRom ICS boot logo. At start up there is a buzz like a text message comes in and right before the phone fully boots there is a smaller, softer vibration. My phone gets to this point and then freezes and reboots.
Sorry for the long post, but I figured the more information I give, the better my chances of getting some help. The battery was at about 85% when it went into this bootloop so I'm going to try and just have it discharge itself and charge it up and see what happens. Any help would be greatly appreciated. Thank you in advance.
Have you tried clearing dalvik and cache? Sometimes that helps
om4 said:
Have you tried clearing dalvik and cache? Sometimes that helps
Click to expand...
Click to collapse
I can't get to recovery, bootloader...nothing. I can't do anything, it just keeps looping. I can't even turn it off.
Hold power until it turns off and then hold power and volume down, it should boot to bootloader and then you can select recovery. Have you tried to boot in safe mode
om4 said:
Hold power until it turns off and then hold power and volume down, it should boot to bootloader and then you can select recovery
Click to expand...
Click to collapse
I mentioned before that it won't let me get into recovery. It doesn't work
No, you clearly wrote you held power and up. I said power and volume down, they are in fact not the same thing
om4 said:
No, you clearly wrote you held power and up. I said power and volume down, they are in fact not the same thing
Click to expand...
Click to collapse
Sorry I wrote it wrong. i have tried it and it does not work.
What about safe mode? Hold volume down when you get to the splash, it will hang a bit and vibrate then you let go and it will force safe mode
om4 said:
What about safe mode? Hold volume down when you get to the splash, it will hang a bit and vibrate then you let go and it will force safe mode
Click to expand...
Click to collapse
I'll give it a try
om4 said:
What about safe mode? Hold volume down when you get to the splash, it will hang a bit and vibrate then you let go and it will force safe mode
Click to expand...
Click to collapse
It vibrates, hangs, then reboots again.
When you try to get into the bootloader are you sure you're letting go? Once the phone turns off you need to let go of power and then hold power and volume down. Some people seem to think you hold power and volume down till the phone restarts and keep holding it, I don't know how people came to that conclusion.
om4 said:
What about safe mode? Hold volume down when you get to the splash, it will hang a bit and vibrate then you let go and it will force safe mode
Click to expand...
Click to collapse
I got it to go into safe mode, shut it down completely and then got it to go into recovery. Wiped and reinstalled and now it's working. Thanks for your help with this!
Complete noob here, sorry if this is a repost
I haven't been able to find a situation exactly like mine. If there is, I apologize in advance for this being a repost. Yes, I am a stupid noob. I had my EVO 4G LTE on HBOOT 1.19 and I unlocked the bootloader, flashed recovery and did all the necessary steps (including kernel adaptations) to flash CM10. Upon doing this I also got stuck in the bootloop and couldn't access recovery. I took it to a Sprint store and they somehow got it back to TWRP recovery and it's currently at the TWRP menu. Here's the problem: I didn't do a backup before doing any of this and I don't have anything to backup to (shoot me). I'm afraid that if i try to get back to the bootloader menu that I will screw it up even more. What do I do/download to get it back to stock? Any help toward this desperate noob would be extremely appreciated
texmexican07 said:
I haven't been able to find a situation exactly like mine. If there is, I apologize in advance for this being a repost. Yes, I am a stupid noob. I had my EVO 4G LTE on HBOOT 1.19 and I unlocked the bootloader, flashed recovery and did all the necessary steps (including kernel adaptations) to flash CM10. Upon doing this I also got stuck in the bootloop and couldn't access recovery. I took it to a Sprint store and they somehow got it back to TWRP recovery and it's currently at the TWRP menu. Here's the problem: I didn't do a backup before doing any of this and I don't have anything to backup to (shoot me). I'm afraid that if i try to get back to the bootloader menu that I will screw it up even more. What do I do/download to get it back to stock? Any help toward this desperate noob would be extremely appreciated
Click to expand...
Click to collapse
load into fastboot and try to flash a boot.img and the stock rom (there a multiple threads/guides on how to do this) this guide is for the one x but it is the same for evo lte http://onexroot.com/one-x-roms/how-to-install-rom-and-boot-image-on-htc-one-x/
stock roms available here http://forum.xda-developers.com/showthread.php?t=1766628

Help - stuck in death! :(

Hey guys,
I was running the newest Paranoid Android 3.60 with DoriMax kernel and decided to switch to the latest SiyahKernel. Unfortunately after installing the kernel through cwm and rebooting all I got was a blank screen after the SiyahKernel logo.
Now heres my problem, normally I would just boot into cwm and reinstall a working kernel, however, I stupidly forgot that my home button is not working! So now I have NO way to boot into cwm and the phone will not boot,
What are my options here guys? The phone is dead?
Cheers
i only see a jig as a solution, which forces your phone into download mode
molemanmus said:
Hey guys,
I was running the newest Paranoid Android 3.60 with DoriMax kernel and decided to switch to the latest SiyahKernel. Unfortunately after installing the kernel through cwm and rebooting all I got was a blank screen after the SiyahKernel logo.
Now heres my problem, normally I would just boot into cwm and reinstall a working kernel, however, I stupidly forgot that my home button is not working! So now I have NO way to boot into cwm and the phone will not boot,
What are my options here guys? The phone is dead?
Cheers
Click to expand...
Click to collapse
Here's a tip :NEVER FLASH WITHOUT WORKING HARDWARE BUTTONS!.Change your HOME button.Or follow along,and read the next message to the quote.
WardenBerret said:
i only see a jig as a solution, which forces your phone into download mode
Click to expand...
Click to collapse
No,there is a way to enter Download mode.You can try something.....turn off phone,and pull out/re-instert battery.Don't turn on yet!Now start pressing and holding the VOL DOWN button only.With phone turned off,and pressing the VOL DOWN key,put in charger.Keep holding the button,until you see Download mode.
GamingDj said:
Here's a tip :NEVER FLASH WITHOUT WORKING HARDWARE BUTTONS!.Change your HOME button.Or follow along,and read the next message to the quote.
No,there is a way to enter Download mode.You can try something.....turn off phone,and pull out/re-instert battery.Don't turn on yet!Now start pressing and holding the VOL DOWN button only.With phone turned off,and pressing the VOL DOWN key,put in charger.Keep holding the button,until you see Download mode.
Click to expand...
Click to collapse
Thank you my friend!

[Q] S4 keeps booting into recovery

Hey everyone, my S4 is running TWRP and it was fine until just now...it keeps freezing when I boot into recovery in which I have to do a battery pull...on top of that, when I pull the battery and put it back in, I'll power it on and it will automatically boot into recovery without me doing anything! Idk what to do, should I have used CWM instead? This is a never ending loop cycle now! Please help!
Iskateforfree said:
Hey everyone, my S4 is running TWRP and it was fine until just now...it keeps freezing when I boot into recovery in which I have to do a battery pull...on top of that, when I pull the battery and put it back in, I'll power it on and it will automatically boot into recovery without me doing anything! Idk what to do, should I have used CWM instead? This is a never ending loop cycle now! Please help!
Click to expand...
Click to collapse
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
THANKS SO MUCH! I think something is messed up with TWRP cause it's been acting funny lately and now this happens.
Failing to boot
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I installed Hyperdrive RLS10.2 on my Verizon GS4 and tried to reboot, but now it shows me the Samsung custom boot and simply recycles doing this. If I boot to download mode, and deselect download it goes into the same loop.. Any suggestions on how to fix this?
HELP! Recovery bootloop, no adb, no odin, no kies
wally44 said:
I installed Hyperdrive RLS10.2 on my Verizon GS4 and tried to reboot, but now it shows me the Samsung custom boot and simply recycles doing this. If I boot to download mode, and deselect download it goes into the same loop.. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same EXACT problem here. Tried to install the new TWRP 2.6.3.1 to prep for a 4.3 ROM install. TWRP suggest a goo install .The Goo install ran through, goo was back to it's main menu and i hit reboot recovery, but still had 2.6.0. So, I renamed the 2.6.3.1 img and put it in the BHP090808_I545_ALL_IN_ONE_TOOL all in one dir, then flashed it through that. Went fine, odined it in, then rebooted into recovery like usual..... Except, recovery never comes up. it just sits there with the Recovery Booting.... thing and Samsung custom screen FOREVER! I tried to use all in one tool to reflash 2.6.0 and it fails becasue odin doesn't see the phone, even thought it's sitting on the booting recovery screen. Tried button hold to get into download, same problems, I get the vol up prompt, hit vol up, get the d/l mode screen for 1-3 secs and then it just reboots itself - into recovery booting screen if i don't try d/l mode,.And odin doesn't see it while the d/l mode vol up msg or d/l active screen is up. Only way to stop bootloops temporarily is batt pull.
So to summarize, recovery bootloop but never gets to recovery, adb can't connect, odin doesn't see the phone at ANY time, during recovery booting, d/l mode confirm screen, or short time of d/l mode screen itself, and I have no tarball to odin a twrp recovery in even if i could get odin going b/c they only offer img files now. Oh, and Kies doesn't even see the phone due to mods. ANY help would be GREATLY appreciated!!
Also, after batt pull, phone sits with blank screen even when on charger/usb and i get a vibrate every 3 seconds continuously.
:crying:
Suggestions?
I545 loki'd, TWRP (read post), HyperDrive 9.1 MDK (which I'd like to keep at nearly any cost)
TIA, for all your conisderation and previous, current, and future help! :good:
same exact problem on tmo
I tried to flash a cm nightly, and then tried to restore it. then this problem occured. any help?
Use Flashify to install TWRP. Goo hasn't worked correctly for some time now.
FernBch said:
Use Flashify to install TWRP. Goo hasn't worked correctly for some time now.
Click to expand...
Click to collapse
This. Flashify is a really good app to use for flashing twrp and will even download for you.
But how are you supposed to use flashify if you're stuck in a boot loop.
twrp keeps booting into recovery mode, I can't get it to just load up my phone OS (CM12)
How do I get my phone to run.
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Click to expand...
Click to collapse
I know this is a ghost thread, but my wife still uses an S4 and somehow it got into the configuration where it would only boot into recovery mode. This trick worked, in fact, I didn't even get the question about booting into download mode; it just booted normally.

Accidently upgraded to VRUEMK2, now phone is stuck

Accidently installed the new update that was pushed onto my rooted phone and now phone is stuck on "Downloading..Do not turn off target!!. Anyway to rollback or fix this error so I can reboot normally". Help is appreciated.
SpunkyXL said:
Accidently installed the new update that was pushed onto my rooted phone and now phone is stuck on "Downloading..Do not turn off target!!. Anyway to rollback or fix this error so I can reboot normally". Help is appreciated.
Click to expand...
Click to collapse
First, try holding down the power button until it turns off. Then try powering it back on.
If it continues to boot into downloader mode, flash the no-wipe MJ7 image using ODIN, and cross your fingers.
Do a battery pull. When you turn the phone on, hold power and volume down (?) to boot into download mode. Then just cancel. It will get you out of that loop. Worked for me. Good luck.
alevere4 said:
Do a battery pull. When you turn the phone on, hold power and volume down (?) to boot into download mode. Then just cancel. It will get you out of that loop. Worked for me. Good luck.
Click to expand...
Click to collapse
i have had to do the same thing a few times.

[Q] Unusual Booting

Started out with Z4, updated to Z8. I tried this with TWRP installed after making both EFS backup and regular nandroid backup, installed fine. I made sure to use the recommended partition zips. Here's the ROM I used. However after turning my phone off it will turn on into safe mode (lollipop) in limited, seemingly random instances. I have yet to access recovery. However, the one part I know that I screwed up is I installed xposed (forgot to install the xposed helper), so I receive unlimited errors for that and can't do anything.
I've tried rebooting my phone normally, rebooting into recovery, and cutting all of my losses and flashing back to stock. Any advice? I'm trying to follow the directions here to revert back to stock, but my computer will only recognize an unrecognized device.
Thanks for the help!
Flash the rom labeled "BarePop_TE_V1 " it has the files need to fix your issues (make sure to thank @engine95). Heres the link to the rom it is pretty much a debloated version of that lollipop rom you were running:http://forum.xda-developers.com/sprint-lg-g3/development/barepop-zv8-t3035551
That reboot problem you are having is because of a bug with the stock rom so just flash that one to fix everything.
I appreciate the help, however my main problem still lies with the fact that I can't access recovery. I've gotten it to where I can reboot normally (albeit I still can't do anything due to the constant errors), but holding pwr+vol down and then letting go and reclicking those once the lg sign comes up won't let me into recovery. Do you have any advice for that? Thanks again for the help!
1619415 said:
Flash the rom labeled "BarePop_TE_V1 " it has the files need to fix your issues (make sure to thank @engine95). Heres the link to the rom it is pretty much a debloated version of that lollipop rom you were running:http://forum.xda-developers.com/sprint-lg-g3/development/barepop-zv8-t3035551
That reboot problem you are having is because of a bug with the stock rom so just flash that one to fix everything.
Click to expand...
Click to collapse
I appreciate the help, however my main problem still lies with the fact that I can't access recovery. I've gotten it to where I can reboot normally (albeit I still can't do anything due to the constant errors), but holding pwr+vol down and then letting go and reclicking those once the lg sign comes up won't let me into recovery. Do you have any advice for that? Thanks again for the help!
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
I've tried doing that a few times as well, it just boots up as normal at that point. I'm welcome to trying anything though so if you have any other ideas, please let me know.
bdpope88 said:
I've tried doing that a few times as well, it just boots up as normal at that point. I'm welcome to trying anything though so if you have any other ideas, please let me know.
Click to expand...
Click to collapse
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
I don't know why it worked this time... but it worked on my second attempt! I have access! Only issue is the touchscreen is messed up on the ROM, but it works!
With all of these issues you may want to flashtool back to ZV4 and reroot or ZV8 your call.
bdpope88 said:
I don't know why it worked this time... but it worked on my second attempt! I have access! Only issue is the touchscreen is messed up on the ROM, but it works!
Click to expand...
Click to collapse
That's a step in the right direction!
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
Not to be redundant, but my understanding is the only way it will go into recovery from full off is to keep holding power+vol down until you see "recovery mode", if you let up on the buttons before you see recovery mode it will simply reboot.
When rooting an ATT G3 I could not for the life of me get it to boot into recovery using the button combo, instead I just used adb reboot recovery instead, worked every time, to this day the guy can only reboot to recovery from within rom, gonna suck if he gets soft bricked.. My Sprint G# holding the buttons works like a charm
When I want to boot into recpvery I always have to do volume + power up until the lg logo comes up then let go and press them again. Then I have to press the factory reset button and click yes. For me and I guess others when you hold volume + powerdown you just end up going into safe mode. If you end up always having problem just download a app that can make your phone reboot itself or download terminal and run:
su
reboot recovery
That always works because it is built into the phone.
1619415 said:
When I want to boot into recpvery I always have to do volume + power up until the lg logo comes up then let go and press them again. Then I have to press the factory reset button and click yes. For me and I guess others when you hold volume + powerdown you just end up going into safe mode. If you end up always having problem just download a app that can make your phone reboot itself or download terminal and run:
su
reboot recovery
That always works because it is built into the phone.
Click to expand...
Click to collapse
For me if I go into recovery by volume down + power. It just goes into recovery.
If I'm using phone, i use terminal command. su -c reboot revovery
I'm using ls990 gold edition.

Categories

Resources