Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.
AugustJuly said:
Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.
Click to expand...
Click to collapse
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Sadly, that's one of the first things I tried.
Thanks for the idea though.
Related
Hey guys
I'm running MrGarak's fantastic MIUI rom however I've found that the kernel is booting my phone into that white HTC diagnostic screen by default. Unfortunately my volume down button is dead and so I can't navigate the menu; the only way I can boot my phone at the moment is to boot it connected via USB as that makes it boot to Recovery and I can reboot from there.
Any ideas? I think this and another rom I tried both used LordMUE's kernel, could that be the reason the boot preferences don't default to just booting the OS?
Any help and/or pointers would be greatly appreciated
So you can access bootloader and recovery!
So just flash another kernel. What's your problem?
Put a zip on your SD (with a SD reader or ADB pull), then go in recovery, navigate with the 4 keys under the screen (or vol+ and power)... and flash.
What is strange for me is that it seems to happen sudenly... so how do ou know it's the kernel. Anyway...
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
_david_94 said:
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Unfortunately it boots into the white HTC area (dunno what it's called). The one where you can see if your phone is S-OFF or not.
Also, I'm not sure what is to blame... but I've only just recently noticed that my phone cold boots this way so I assumed it was a recent rom that I applied. Will test this theory later.
Sounds to me like your volume down button is stuck in.
Definitely not a ROM issue, as it has nothing to do with the bootloader.
Sent from The App that Time Forgot.
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
xtremedelta said:
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
Click to expand...
Click to collapse
Ah, I'm definitely beyond warranty. The thought of vol+down being stuck down makes a lot of sense!
I'll just take it to one of the dodgy Asian repair shops, if it's a hardware issue I'm sure they'll know what to do.
Cheers for your help everyone!
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
Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Clodio69 said:
Need some help please !
First of all I'm stuck in bootloop with my nexus 7 2013 (not unlocked). So I pluged my N7 in my computer (windows 7) to flash the Rom. I also have a problem with the driver when I connect my N7 to the computer and I get the message (MTP device failed ). So I've tried to install manually new drivers from Google but it says that my drivers are up to date ??? Now It seems that it's impossible to flash my N7 if my computer doesn't recognize my device.
What is the best thing to do now
thanks in advance
claude
Click to expand...
Click to collapse
Well, it looks like you have a couple of things going on. I can't remember how I got windoze to recognize the n7, but it had something to do with deleting the driver then plugging the n7 back in and letting it install the driver again. I remember I had to play around with the thing for a little while. Trying to update the driver wouldn't work for me either. As, far as the bootloop, you could try this one click tool: http://forum.xda-developers.com/showthread.php?t=2381582 Finally, you could try wugfresh's toolkit if you want to take the lazy route. It actually works pretty well. It might even help with that driver issue. http://forum.xda-developers.com/showthread.php?t=2389107 you don't use it to install a rom, but you do need to install a custom recovery and the toolkit could help with things like that. I personally use the toolkit to return a tablet or phone back to factory condition, lock the bootloader, etc...
You could also try to do a factory reset from the stock recovery. That fixed a boot loop for me after unlocking my bootloader.
Problem solved
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Thanks
Claude:laugh:
Clodio69 said:
I finally contacted Google Canada Monday morning and spoke with with a tech. Wow...very impressed by the service and my problems are now solved. First we went to Recovery mode ( Power and volume down) in that mode you then press again power and volume up and release at the same time. Then,from that menu you can now swipe all data and it solves the Bootloop problem. Finally I reinstalled all my app and back to normal. I pluged my N7 to my computer and now no more driver problem....
Click to expand...
Click to collapse
That's what I was referring to in my post, sorry for not giving a more detailed explanation.
Glad to hear you that you had a good experience with Google support and that you solved your problem. :good:
Thanks for giving feedback and have lots of fun with your N7!
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
frozst said:
Hello!
I'm stuck in a loop boot too. I flashed without wiping... I try to boot in recovery mode but it's impossible. The combination vol up, down and power doesn't work. It tries to boot as usual so starts in a loop again.
Sent from my Nexus 4 using Tapatalk now Free
Click to expand...
Click to collapse
Let me get this straight....are you trying to hold volume up & down at the same time? If so, you cannot please both volumes at the same time. Also, to boot into the bootloader (same as fastboot, not recovery) is power + volume down. The easiest way to do this is to hold volume down, then press and hold the power button. If the tab was on, and the screen goes black, let go of the power button, but keep holding the volume down button. It should boot into the bootloader soon enough.
1. Push volume up and power button for 5 seconds then release the power button.
2. Do a complete wipe of the system and reinstall the system.zip again and reboot.
If it doesnt load the recovery do this.:
1. Hold volume down and power button for 5 sec. Release the power button and volume once you enter the download screen.
2. Use odin in your Pc to install the rom you want or stock rom.
(3. If you installed stock rom go back to the steps I wrote at the top and flash a new rom)
Remember that you need to be rooted.
OK so I was trying with the wrong combination.
With both vol up/down + power worked.
I restored and it's up and running again.
Thanks!
Sent from my Nexus 4 using Tapatalk now Free
Ok folks, normally I figure these things out but this one has me a bit concerned.
I was in ViperROM HUB and installed a font package, it needed to restart in recovery to install, so I allowed it. I turned to my computer and when I next looked at my phone the screen is off and refuses to come on. When depress the power button I get a vibration feedback but the screen won't come on. I tried VOL DOWN and POWER but nothing is happening. Im gonna let the battery run dead and see if that will resolve it.
Has anyone encountered anything like this before?
3NE said:
Ok folks, normally I figure these things out but this one has me a bit concerned.
I was in ViperROM HUB and installed a font package, it needed to restart in recovery to install, so I allowed it. I turned to my computer and when I next looked at my phone the screen is off and refuses to come on. When depress the power button I get a vibration feedback but the screen won't come on. I tried VOL DOWN and POWER but nothing is happening. Im gonna let the battery run dead and see if that will resolve it.
Has anyone encountered anything like this before?
Click to expand...
Click to collapse
Hey!
I dont think its bricked.
Ghost helped me out with my problem, see below solution.
Try holding POWER + VOLUME UP for 20 seconds and it should restart.
However my case was different I was stuck in HTC logo screen and no way to restart.
On the M8 it is Power and Vol Up to perform a "battery pull".
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Thanks grega_slo and gaiden0000 for the quick response and spot on advice.
I did that before but it didn't work, it works now…guess I didn't hold VOL UP long enough.
Yeah I didn`t know about VOLUP either
It scared the crap out of me when I S-OFFed the device and was stuck haha
grega_slo said:
Yeah I didn`t know about VOLUP either
It scared the crap out of me when I S-OFFed the device and was stuck haha
Click to expand...
Click to collapse
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?
cquinn said:
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?
Click to expand...
Click to collapse
Fastboot clear cache and format eternal storage youll be good
Sent from my One M8 using XDA Premium HD app
cquinn said:
having the same problem. flashed cyanogen nightly and when it rebooted got to the splash and then black. nothing. none of the above methods seems to bring it back. I can hold the power and vol up and get the splash to reappear but still goes to black. any thoughts of have I really bricked this phone?
Click to expand...
Click to collapse
Put the usb cable in then press vol up and power until it restarts. As soon as you hear the ding on your pc press and hold vol down and power, you should then boot into hboot MENU.
pbedard said:
Fastboot clear cache and format eternal storage youll be good
Sent from my One M8 using XDA Premium HD app
Click to expand...
Click to collapse
when i use this either from fastboot or adb command prompt all I get is < waiting for device >
---------- Post added at 08:18 AM ---------- Previous post was at 08:10 AM ----------
ashyx said:
Put the usb cable in then press vol up and power until it restarts. As soon as you hear the ding on your pc press and hold vol down and power, you should then boot into hboot MENU.
Click to expand...
Click to collapse
never seem to hear a 'ding' or any other sound but no matter how I time it - power/vol up then power/vol down still results in htc splash then just black. Phone was quite warm (not quite hot) when I went to bed last night and this morning battery was at "0". When I first plugged it in and pushed the power button it alternated from the battery charging display to the TWRP locked screen but I couldn't seem to get it to stay on the TWRP screen no matter what I did. Now that I've used power/vol up I don't seem to get the battery or TWRP. just black or when trying power/vol up I get the splash. Power/vol down gives nothing - just black
EDIT: Just tried - let battery go dead. Plug in to computer hold power/vol down. Screen goes from battery icon to blank and back to battery icon.
EDIT: Pulled and reformatted sd card in Evo 4g LTE. Retried fastboot command still just shows "waiting for device". Even tried adb reboot bootloader and reply "device not found"
Could I use adb to reflash ruu? If so would the command be adb flash (filename)
Was beginning to lose hope of ever fixing this but a HUGE shout out to Simer03 who provided the critical piece of information - namely - add a ROM zip to your sd card. Hope nobody else ever has this problem but just in case
Post #4 here
Nothing is going to work unless you can either enter the boot loader or boot into the os.
You should still be able to access hboot unless that is corrupt. At the very least you need to hear the ding on your pc so you know the pc has recognized your device is connected.
Try again with vol up and power, hold until it reboots you should then hear that ding. If not check you have the necessary usb drivers installed on your pc or try a different usb cable.
Started two days ago. Phone would randomly power off and boot back up. Finally it shut off and would not power back on. I had Cm11 installed with CWM 4.0.4.6. The phone powers on after inserting the battery. The Samsung logo flashes and then it shows the "Galaxy S3" logo with the CM logo below it. The phone the powers off. I have done a factory reset, cleared both caches, formatted the system folder, flashed SlimKat from recovery and tried another known good battery. At this point I figured I would reflash CWM but if I put the phone into download mode, it powers off after just a few seconds as well.
If I boot the phone into CWM, the phone stays on as long as I want it to so it makes me think this might be fixable. Just need some help.
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
DocHoliday77 said:
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
Click to expand...
Click to collapse
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
kylelever said:
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
Click to expand...
Click to collapse
It can be replaced fairly easily, just look it up on youtube.
You can buy the part off Ebay (or any other site you might prefer) for fairly cheap.