I have attempted to install Cyanongenmod 10 and Gapps using CWM on my phone and it appeared to have worked correctly. I was in the process of getting my apps setup when the phone restarted and has gone into a persistent boot loop. It has probably rebooted well over 1000 times now.
On most loops it shows the white Samsung logo and then reboots again after about three seconds.
If plug it into USB, it shows the charging battery icon, then the full Samsung Exhibit 4G logo (for a split second) and then reboots.
If I remove the battery and then reinsert it, the phone powers on and goes into a boot loop without me even touching the power button.
I have attempted getting into recovery using both the battery removal + volume up key and using the power button and volume up key methods. Neither work. (Actually it worked once out of about hundred attempts but then immediately rebooted before I could do anything)
I was concerned that it might be a hardware problem with the power button, but I have inspected this closely by opening up the phone as as far as I can tell it is fine.
Any ideas for next steps (including getting a new phone) would be appreciated.
Additional Information
I should add also that I can get into Download mode, but again the phone reboots within seconds before I have any opportunity to do anything
Look here. http://forum.xda-developers.com/showthread.php?p=48658330
Sent from my SGH-T679 using xda app-developers app
Thanks Dvarl.
I had, in fact, seen the thread that you referenced and tried what was suggested. The symptoms certainly sound identical. However, I found that even with the case removed so that no pressure could be applied on the power button, the symptoms persist. So the trick with the tweezers and file is not going to help my situation.
Any other ideas?
ilopata1 said:
Thanks Dvarl.
I had, in fact, seen the thread that you referenced and tried what was suggested. The symptoms certainly sound identical. However, I found that even with the case removed so that no pressure could be applied on the power button, the symptoms persist. So the trick with the tweezers and file is not going to help my situation.
Any other ideas?
Click to expand...
Click to collapse
It definitely seems like the power button. Something is triggering it, even though there is no pressure on it. Otherwise, it would not reboot when you are in recovery, or every three seconds.
Related
Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD
When I tried to disable the voodoo lagfix my phone froze, after about 20 minutes i decided to pull the battery and now the phone freezes when trying to boot and even after plugging in the charger, it freezes on the battery load symbol. Unfortunately, the 3 button way to get to the recovery menu doesn't work. help me please??
I'm having the same problem - phone just hung on the kernel load screen (firebird 2) after trying to shut off lagfix - although I can get to a red recovery mode menu. Not that it's helping at this time. It would be nice if I could recover without a clean wipe of the phone.
Anyone have any ideas. I'll be scouring the threads...
You could try making a jig and flashing to stock http://forum.xda-developers.com/showthread.php?t=841512
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
I'd really like to do this without hardware, but making a jig kinda sounds like a fun project and i do have a soldering iron in storage somewhere...
xsamxoxo said:
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
Click to expand...
Click to collapse
I'm afraid not. This happened to someone I know and they told samsung the OTA update bricked it and AFAIK they fixed it for free. They never tried using a jig though, so if you don't want to wait to replace it or anything you could try a jig since it might work and the parts are pretty easy to get (and if you'd be replacing the phone, a jig is ALWAYS good to have anyway)
Just another note to throw in there, the computer recognizes the phone, but strangely my computer freezes while trying to read the media storage drives. I can't tell if the internal sd is mounted because of the ever-lasting wait but i'm almost positive its not.
Do adb commands work?
Sent from my SGH-I897 using XDA App
Thnikk said:
Do adb commands work?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, it says "error device is offline"
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
avgjoegeek said:
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
Click to expand...
Click to collapse
it connects even though the phone is frozen. I'm heading over to "The Shack" pretty soon and just making a jig.
Thanks for all your help everyone.
Edit: Just confirming that with much dedication and a steady hand I finally have my captivate up and running with the help of the resistors. I also flashed the 3 button fix stock rom.
Well, I kept trying the least invasive methods first. Tried to reflash Firebird. Then went adb and such. In the end, it was pretty clear that it had hung at the lagfix correction, and I was dealing with a file system error. I was eventually able to get into download mode. The hardest discovery was finding that I had gotten the wrong drivers from samsung. The ones in the [stock rom] odin master clear page were what I should have been using. When I loaded those, the computer recognized that I had a phone and not a "serial gadget" and then I knew I was close. Odin finally saw the phone, and a couple tries at "light" re-stocking failed at file analysis, so I did the repartition (aha, file system error), and it shot through the whole process and I had my phone back and flashed to Serendipity in about 20 minutes.
But I would like to know about the red menu. That was unexpected (blue for standard, green for cwm).
No need for a jig. I had access to some phone functions, most importantly, download mode.
So I made the mistake of dirty flashing the new viper rom 1.1.0 on top of 1.0.4. Got stuck in a boot loop then on the viper screen. Yes it's my fault for dirty flashing however I was stuck on the viper logo for over 30 min. I tried holding down power over 10 seconds a bunch of times. Kept trying & trying. Waited a while it finally took a reboot after dozes of trys. So my phone is not taking the simulated battery pull correctly. Even was the rom was working perfectly I would try it while booted & the screen would come up to keep holding to reboot but the phone would never actually reboot. It always worked perfect on my evoLTE and the entire point of it is if your phone is jammed up you have an out. So if it's just my phone it must be a hardware issue, anyone else have trouble with there phone? If it is just my phone I wanna get it swapped out cause it can lock up even when doing everything right and I don't wanna have to wait for the battery to die.
Try with the down volume key pressed as well. Sometimes the power button itself hasn't worked for me. But with the volume key it always works for me.
Sent from my HTCONE using xda app-developers app
NuttyLemonz said:
Try with the down volume key pressed as well. Sometimes the power button itself hasn't worked for me. But with the volume key it always works for me.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I tried that too many times. I already re-locked, flash backed to stock gonna bring it in. The phone just refuses to accept a force restart. I attached a screen shot, the phone will just continue to sit on that message until I let go and never reboot.
Just got back from Sprint store, of course it works perfect every time I'm in there. I can't expect them to swap it when it's working. I hate going there, the guy says to me just hold the button to the menu comes up to reboot it. Tried explaining what a fail safe was he didn't seem to get it. Gonna unlock again and just be careful about dirty flashing it was my fault that it got stuck in a boot loop anyway but I still expect the fail safe to work, it always did on me evo LTE
My Galaxy Exhibit II 4G is about a year old, rooted and i have CM11 installed. Everything was fine, I had it plugged in (charging) and i was downloading an app (Camscanner) from the Mobogenie store when suddenly the phone shut off and the battery icon appeared with the loading circle in the middle.
This did not stay on for long as the screen would go off and this would again appear. After pulling the battery and removing the charger, then reinserting the battery, the phone would just flash the SAMSUNG logo in this very same manner.
I am unable to get into either recovery or download modes and when i try this combination (VOL UP + VOL DWN) i get:
RAMDUMP MODE
Cause: Force Upload
I have been reading forums for hours and i have found nothing. Is my device bricked? What can I do to recover it? Please, any help would be greatly appreciated :crying:
What happens if you try vol. up + power, or vol. down + power?
jfbs said:
What happens if you try vol. up + power, or vol. down + power?
Click to expand...
Click to collapse
Thanks for replying. Nothing happens. It just continues to reboot like I'm not doing anything. The only way I'll get a reaction out of it is with vol up + vol down
It can be tricky. This post may be clear http://forum.xda-developers.com/showpost.php?p=32437850&postcount=6
The link you sent me to sounds similar to my problem, except I wasn't trying to update the firmware. The crash was spontaneous.
However, neither of those methods work. As soon as I put in the battery the SAMSUNG logo appears, then disappears and reappears and it continues like that... Pressing the power button does nothing, whether by itself or with the volume up/down button
I am beginning to panic
What happens when it's connected to power?
Adrian Gobourne said:
...battery icon appeared with the loading circle in the middle.
Click to expand...
Click to collapse
Anyway, after many hours of investigation I discovered it was a hardware problem. The power button was stuck and so it forced it to reboot repeatedly. It also explains why it (the power button) was unresponsive. Disassembling the phone and freeing up the power button solved the problem.
P.s. Your build of CM11 is boss
I have same problem with power button. Had to tweak it hard cause it was so sensitive.
It's the first time it's happened to me. Probably because I dropped it so many times
Strange, ...
Adrian Gobourne said:
My Galaxy Exhibit II 4G is about a year old, rooted and i have CM11 installed. Everything was fine, I had it plugged in (charging) and i was downloading an app (Camscanner) from the Mobogenie store when suddenly the phone shut off and the battery icon appeared with the loading circle in the middle.
This did not stay on for long as the screen would go off and this would again appear. After pulling the battery and removing the charger, then reinserting the battery, the phone would just flash the SAMSUNG logo in this very same manner.
I am unable to get into either recovery or download modes and when i try this combination (VOL UP + VOL DWN) i get:
RAMDUMP MODE
Cause: Force Upload
I also get ram dump mode error when trying to manually boot recovery.
I have been reading forums for hours and i have found nothing. Is my device bricked? What can I do to recover it? Please, any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
OK so I'm no expert or anything but maybe my experience with this Model might be able to help you a little bit. I have the same model and it was doing the exact same thing however I haven't rooted it. And I've since corrected the issue on mind particularly it appeared that it was the charge port and/or USB that either had a bad connection or possibly it was boot looped. However with me not rooting the I didn't understand how it could be booted Looped so I started playing around with holding the power button playin with USB things of this nature and what I found was that if I hold the USB to one side either left or right, this allowed me to help a boot farther into it sequence at first to just show the Samsung logo over and over then I could get it to get to the boot sequence about halfway through the boot animation until I finally got to the exhibit screen where displays its model and 4G status. I accomplish this by holding the USB to one side and pushing and holding the power button intermittently throughout the boot. Once I hit the unlock screen unlock the device and I immediately factory data reset it. I'm under the impression that mine was possibly I think that mine was somehow a corrupted bootloader or software still I don't know what caused it to backed up to this day occasionally it'll shut itself down and reboot on me that's why I'm here today I've got all the parts and pieces I need to flash a new rom and hopefully new software the new work over I'll be good to go I also cleaned the USB port made sure that it was still snug to the board all of the good stuff. I don't know if it'll help you but I had the same situation I thought you'd like to know that it was probably not what you were doing with the phone it may just be the software itself with this particular phone see I done nothing that you didn't had the exact same problems. I hope it was somewhat helpful if you haven't gotten it unlocked or re-booted yet. Then maybe just play around with the power sources and power buttons. And see if you can get the same results I did
Hi all,
Putting up this post because I am at my wits end! I have had my Galaxy Tab S2 now for about a month. Just recently I would be using it and it would seem to start lagging a bit, and then without warning it would basically either power cycle, or just freeze and power off. Upon restarting, everything would go as per normal, and then after a few minutes it would happen again.
Went through the process of backing everything up so I could factory reset. This was a strange experience. The files would begin transferring to the backup media, and then the process would freeze, and the power cycle happen again. What made it strange was that if I kept touching the screen, the transfer would continue. Leave it to its own devices and it would freeze and power down or power cycle. Anyways, managed to get what I could off it. On to a factory reset.
Ensuring it was off, I pressed the power and volume up buttons, ending up with a screen with the android robot. Then it shows a screen with the android robot on its side and an exclamation mark above it. Finally to the recovery screen. Here things got a bit hinky too. I would use the volume up/down keys to move through the options available, and then found that the up/down buttons became unresponsive. Frustrated I touched the screen a couple of times and what do you know, the selected choice would move according to what volume button pressed. OK that's weird, and what do you know, after a while it reboots irregardless of choice.
Finally managed to get it to factory reset, wipe everything and on start launch into the setup procedure. "Yay" thought I, "Nay" thought the tablet. Now i'm stuck with a tablet that gets about halfway through the process, freezes, then reboots or powers off. Thing is, it ALWAYS seems to happen at a point in which keyboard interaction is required. I get about halfway through typing my name and snap.
So yeah I have no idea. I'm thinking it could have something to do with battery, however, this all still occurs even if it is plugged into a source. So before I go about trying to work out how to get the back off, I thought I would ask for some advice here!
Seriously, any suggestions would be greatly appreciated!
Cheers,
Chyr0n
Get a new one.
Sent from my SM-T710 using Tapatalk
Yeah, it's new and is not rooted. Why not going thru warranty and get a new one?
Sent from my SM-T810 using Tapatalk