I had dzks CM10 port running and for some odd reason while I was playing with the settings it froze. I ended up taking to battery out, upon turning it on it stopped booting. It would get to the CM10 boot screen sometimes, but even then it would freeze.
So then I sbf'd it back to 2.3.6 stock and rooted, bsr and installed Eclipse (As I figured that the port of CM10 was too unstable and just broke or something) it worked for a few hours but then it froze again. So I again took out the battery and the same thing happened. I sbf'd ANOTHER time because I figured stock can't be too bad, right? but now it's stuck on the Motorola "Dual core technology" screen and doesn't get passed that. On rare occasions the screen will be on, but it will just go blank. I've noticed even on the boot screen the phone makes the sound when it gets plugged into the computer (When it is plugged up to the computer) it makes the vibration the happens after the boot. I've done the factory reset dozens of times and even Sbf'd at least 5. Nothing is working, I really need help.
Related
I picked up a used Vibrant last week and it initially worked fine. However, it still had 2.1 installed so I decided to update to 2.2 with Kies Mini. After 4 hours of screwing around and with it and much searching of forums, I finally got it upgraded, but something seems to have happened to the phone in the process.
The phone acts like the USB is permanently on, even if no cable is attached. The USB plugged in notification stays on even when the cable is unplugged. After I charge the phone and unplug it, the battery indicator continues to show that it is charging. The main problem is that the phone gets stuck in some kind of loop when the phone is turned off and never truly turns off. Initially, what would happen was that the little loading circle indicator would appear then the battery charging icon would pop up for a moment. However, since there was no cable plugged in, it would disappear. After several seconds of a black screen, the loading circle would come back up. This loop would simply continue over and over. Pulling the battery and putting it back in did nothing; the loop would just start over again the moment the battery was inserted. The phone would not respond to the power button while this loop was going.
At this point, I was still able to get the phone to boot by plugging in the USB cable, waiting until it started to charge (with the green battery icon) and then hitting the power button. This went on for several days. Today, I decided to take the battery out for several hours to see if anything would reset. However, things only got worse. The loading icon still pops up but now the charging icon doesn't come up, even if the USB is plugged in. I just get a loop where the loading circle pops up, disappears, comes back, and so on. I am now also not able to power on the phone with the power button.
I am still able to get into download mode (but not recovery mode) so I flashed everything back to stock using Odin and the instructions on this forum. This does get the phone booted back up, but as soon as I turn it off again everything starts all over.
So now I have a phone that, if it is ever turned off or loses power, has to be reset, wiping everything in the process. Does anyone have any idea how to fix this? Is it some kind of bootloader issue?
Odin, put 2.1 stock rom back.
Like the post before me mentioned, Odin back to stock 2.1
And personally, I'd much rather install stock froyo with ODIN rather than KIES.
Or just use a Custom ROM altogether.
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
mordrid52 said:
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
Click to expand...
Click to collapse
I have heard of KIES updates screwing phones before! I would contact T-mobile and tell them the situation....letting them know its used and had stock T-mo 2.1 and after using KIES to upgrade to 2.2 it screwed your phone.
Eventhough its used and You didnt buy it from them, they would probably fix it for you for free since their update program caused the issue...If it was a stock phone then they will probably fix it.
edit: in your story to them, leave out the part about you using ODIN...i am sure they will call that a void of the warranty.
I recently flashed CM10 onto my Nook Tablet - thanks to all those who helped!!
Everything was working perfectly for about 1 week, then the kids ran the battery all the way down. I plugged it in to charge it, and it started doing funny things. As soon as I plugged it in, it would turn on to the initial screen with the sliver N, then it would turn right back off (presumably because the battery was drained). It just kept repeating this. I didn't do anything because I figure that once it charged everything would be back to normal. However, I turned it on the next morning and it started walking me through B&N's initial setup. My CM10 is gone and I'm back to stock OS. What happened, and how do I prevent it from happening again?
(I was surprised that the stock OS was even still there.)
I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.
asawi said:
I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.
Click to expand...
Click to collapse
Is there a way to stop the table from automatically trying to boot when it's plugged it - maybe this will correct the problem when trying to charge a fully-drained battery. Is there any reason I shouldn't do this (assuming it's possible)?
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
zefir738 said:
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
Click to expand...
Click to collapse
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
kaljr1980 said:
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
Click to expand...
Click to collapse
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
zefir738 said:
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
Click to expand...
Click to collapse
I had boot looping problems several times now. For me, it's always been sticky power button. One time, I forgot it had that problem at work and looped for 30 minutes. I just take out the battery for about an hour, then get the power button unstuck. My button gets stuck at the bottom of the button, so I can normally mess with the top part to fix it.
So the issue has escalated even further now. It is a sticky power button, i believe, but now when the phone tries to turn on it shows both samsung logos and then shuts right back off and refuses to turn on again unless i do a battery pull...I'm not even sure if it's turning off, actually. It turns on immediately after inserting a battery into the device. But right now I have a fancy brick.
Definitly a power button issue
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Similar Issue
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
It is probably your battery
cayjominara said:
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
Click to expand...
Click to collapse
The Note won't run without a proper battery installed. I had the problem where I swapped out my dead battery for a fully charged one (I do this everyday) and all of a sudden it kept bootlooping.I spent a few hours, when I got home, flashing it back to stock etc to no avail. I could get into download mode, and download to my hearts content but when I tried to boot the phone, it looped. Samsung, samsung, samsung....
I swapped back my, now charged, spare and BAM it booted into stock android no problem. I think my first (stock samsung battery actually) is finished. Or at least has some serious issues, and the phone refuses to boot with it in but my spare (Anker battery) works fine.
I hope this works for you's, it did for me
---------- Post added at 03:27 AM ---------- Previous post was at 03:25 AM ----------
Also, if I had just charged my phone using my working battery, I would have saved myself some serious grief, and hours wasted. Here's to hoping you don't too!
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
When data gets corrupted, all you can do is wipe and start over. I had to do that once when running Viper as well.
Just a thought in trying to be helpful....
I used that ROM for a while myself and never really had any issues but have had a similar situation.
I pulled my sd card out and backed it all up. Replaced SD card.
Then went into recovery and reflashed the ROM.
Worked solid after that and no explanation as to why it was corrupt/hanging in a loop.
Hope this helps..
billypilgrim said:
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
Click to expand...
Click to collapse
I have that happen several times. Nothing obvious that causes it. Cap'n is right need to wipe and re-flash. Here's the small trick since it just keeps rebooting on you, after you hold power for ten seconds and the screen blacks out. Make sure the capacitive buttons go out as well, that split second they go dark let go of the power button and press vol down and power to get it back into bootloader. Then you can get back in recovery to flash.
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
crovax33 said:
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
Click to expand...
Click to collapse
It could be a power button failure, it's actually quite common on the S4.
Google "Galaxy s4 power button problems"
Check out this link:
http://forum.xda-developers.com/showthread.php?t=1931310