Last night my phone was lagging, but I didn't think anything of it. This morning, it had turned itself off. I turned it on, it stayed on for about 5 seconds, then made a weird noise and rebooted. It does the same thing on reboot and keeps looping.
I booted into recovery without a problem, wiped everything, flashed an old rom, and rebooted. It turns on as if it is still running the old rom and does the same noise/reboot thing. I tried factory resetting with Odin, but it keeps failing. I tried pushing files to the phone through the Android Toolkit, but that's not working, either.
Any ideas? I have no idea what happened or why it's acting as if it's read-only.
GSM Nexus; was running CM11 Snapshot 6.
Just a shot in the dark, is the micro USB port clean? Maybe it's shorting out.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Im having the same problem any ideas how t fix it guys ?
Related
Hey guys,
I'm having a rather strange issue, that seems to have happened overnight. Between yesterday and today, my phone started to act funny out of the blue - random reboots, shut-offs. I figured I might as well try a new rom, and tried booting into recovery mode. To my surprise, it wouldn't work. The phone hangs at the white screen that says "htc" in green. Any idea how I can get back into recovery?
I'm running CyanogenMod 6.1.1.
Thanks.
Try installing ROM Manager from the Market and reflashing the recovery image from there.
No dice, unfortunately Is there a way to force flash somehow? I seem to be stuck. Even factory reset doesn't work :/
If you are using official recovery 3.0.0.5 have you tried turning phone completely off and then plug in your power cable? It shouldn't even boot into the htc screen but go straight to recovery.
Just a thought and goodluck
Sent from my Vision using XDA Premium App
Just tried that - the led turns orange and the phone seems to stay off, but actually freezes. Unless I pull the battery, it won't turn on.
Damn. Don't know what to say. Adb maybe?
Good luck
Sent from my Vision using XDA Premium App
Well this isn't strange at all. I can flash recovery 2.5.1.3 and all is well (I can get to recovery mode, etc.). It won't let me flash 2.5.1.4. And with 3.0.0.5 I have the same issues as in the initial post -.-
This all happened so suddenly the past few days:
1. After flashing AOKP M6, I couldn't mount my phone through USB. I kept getting a "device unrecognized" error, followed by an installation failed error. Wasn't sure what the problem was because my USB was working right before I flashed Milestone 6.
2. I was having random FCs with AOKPM6 + Eugene's kernel so I backed up my data and did a full wipe/reset from CWM. This lead to a black screen on every boot after the Samsung logo faded away, and the ROM wouldn't boot. Freaked out so I tried multiple times with multiple cables and multiple computers to get to ODIN and prevent further damage...
3. Can't get into Download mode for ODIN. I've ODIN-ed my phone at least 2-3 times when official ICS came out for our T-989 so I know I'm doing it properly. When I unplug my battery, plug it back in and hold down both volume keys, it takes me to CWM, not Download mode. I've experienced this before on the Vibrant T-959 and the reason for this would be because the bootloader is broken.
I've heard of Mobile ODIN but it does not support our T-989 :crying:
Obviously my next motive is to send in my phone for replacement for T-Mo but I can't unroot or get back to stock firmware because the USB hub on the phone is damaged. I read elsewhere on XDA that by blowing air into the USB port or by pushing around the connector inside the USB hub with a precision screwdriver, I can temporarily regain USB connection...IT ALMOST WORKED. While my Win7 laptop recognizes my Samsung phone and allows me to mount the SDcards, this same does NOT apply for rebooting to Download mode from the power menu then reconnecting my USB cable when I open up ODIN.
Is there ANYTHING I can do?
Did you flash the Rom again after doing the full wipe?
Sent from my SGH-T989 using xda app-developers app
if not that's explain y it won't boot lol
Sent from my SGH-T989 using xda app-developers app
No I didn't even have the ROM .zip on my phone anymore. Either way I FIXED IT! I woke up earlier and was still content on getting it working somehow. I kept playing around a precision flat head screw driver after putting my phone into Download mode from the power menu. Button combination still wasn't working. My computer and ODIN detected the phone so I flashed right away and tried not moving my phone at all. The first time it lost connection to my phone half way so it didn't install properly and went to a weird alternate Download mode screen that said something like "your upgrade wasn't properly installed, connect to Kies and recovery"...Kies obviously didn't recognize my phone so I saw that ODIN still recognized my phone. Tried restoring from ODIN again and it worked! Went to a bootloop, displaying only the SAMSUNG logo but I went into stock recovery, wiped data/factory reset and everything is okay!
I called TMO to order a replacement- a phone with a working USB hub so I can mount mass storage and whatnot. Weird thing is that this phone's USB is working a-okay. I plugged it into all of my different ports on different PCs and, at least, this stock 2.3.6 TWROM is always asking me if I'd like to mount my phone as removable storage. Both internal and external sdcards are working fine. Very, very strange.
I hope this helps someone who comes across this problem.
**A precision flat-head screwdriver was used to poke the connector sticking in your USB port in your phone (it's the only thing somewhat popping out of your USB port). Don't go too hard, but push the connector up, down, left, right. There's obviously no "right way" to do this so be gentle as not to break it altogether. This is just a temporary fix. I don't know how long this will work for. The first few times I positioned the connector the right way it only stayed that way for a bit and my computer then recognized it as an "unrecognized/unknown device." Now, somehow it's been working for the last 4-5 hours, even after ODIN-ing and unplugging/replugging, etc.
Dude if you wiped the phone in cwm and just rebooted I'm pretty sure that's y you got the black screen after boot. To my understanding when you use super wipe that wiped the Rom off your phone so without flashing another Rom or restoring a nandroid your phone wouldn't boot cause there wasn't anything for it to boot.
Sent from my SGH-T989 using xda app-developers app
I believe u are just using the wrong key combo for download mode. For me its volume down and power for download mode and both volume for recovery.
Sent from my SGH-T989 using xda premium
bobby3306 said:
Dude if you wiped the phone in cwm and just rebooted I'm pretty sure that's y you got the black screen after boot. To my understanding when you use super wipe that wiped the Rom off your phone so without flashing another Rom or restoring a nandroid your phone wouldn't boot cause there wasn't anything for it to boot.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I was using aokp_hercules_unofficial but the seemed to be a problem of it sticking upside down. so i decided to reflash the phone. I tried to load the new rom on the phone but it would not be recognized by my computer. My galaxy s 3 had no problem connecting. so i loaded drop box before anything and downloaded it to the phone. did a back up and then i wiped everything and went to look for the file and could not find it nowhere. i tried restarting the phone and it would not go into cwm at all. the 3 button combo only takes me to odin mode (download) if i try to power the phone it flashes Samsung for a second and stays black. I dont want to have to send it in but if i do it shows no binary custom number and says Samsung official.
So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.
My brothers Galaxy Nexus crashed two days ago and rebooted. Since than whenever you boot it again, it boots normally but after about 10 seconds crashes and reboots again. No matter if you unlock it, SIM installed or not, with external power or not makes no difference. Always keeps crashing and rebooting. So the first thing I did was a factory reset within the bootloader. When it restarted nothing was wiped. Wallpaper, unlock code and all apps were still there.
Weird.
So I decided to flash the the whole stock image again. Downloaded the latest version from Google and flashed it. Took a fairly long time (30 minutes), but had no errors or irregularities and had the same result as the factory reset -> nothing. Everything is still there.
How can this even be? The only thing I could imagine is a broke storage. Is this a possibility?
Thanks in advance
It might be a broken storage. One thing you can try is to flash an older version than upgrade via OTA. Assuming that you have 4.3, you can flash 4.2.2 than via OTA, you can update. I had a rebooting problem before, but it was because of my battery. When I unlocked my bootloader I was surprised to see that my data was still there but when I factory reseted, it was gone. Reply with the results
Sent from my Galaxy Nexus using XDA Free mobile app
Hello, I have been having issues with my SGH-M919 doing a bootloop recently. Since 2014 I have been running CyanogenMod. Overtime it has been working flawlessly. Ocassionally I would make a backup, then proceed to flash the latest nightly rom. Going from CM11, CM12, then CM12.1. Over the past month, or month and a half, I have been experiencing radio issues. The modem would fail to have a decent signal, or I would get no data, and wifi, and/or airplane mode would fail to enable or disable until reboot. Recently, I had notice a conenction issue just a few days ago, and after reboots the radio would fail to initialize. I recieved a call, and it rebooted. So fed up with radio issues I suspected a bad rom configuration. When I rebooted after backing up and flashing the CM12/1 05.14.2015 build, I got nothing but a bootloop. I tried restoring the backup but had the same result. I tried installing a previous rom build with same results. Cleared dalvid cache, and still got the same result. I ended up completely wiping the phone, all options under the wipe options under PhilZ Touch recovery. Upon reboot I was stuck in download mode. Eventually getting odin to repartition without a pit file, it failed using the only available stock rom I had available, odin failed and kies wouldnt cooperate AT ALL. I eventually found a PhilZ mirror cause the site keeps returning "invalidcust" on downloading. So I flashed the recovery and sideloaded the latest rom and got it to boot. After rebooting to install gapps, it worked, then afer setting up google play store, I had noticed I was not getting any data, and upon reboot, bootloop came back. The actual point of reboot/crash varies. Sometimes is hangs a few seconds at the samsung logo, then not even a few seconds after the bootanimation starts... it reboots. and at other times it stays around 8-10 seconds before a reboot. I suspect, faulty hardware, or I need to flash the stock rom to get the hardware to refresh properly.
Any help would be greatly appreciated.
Update:
Upon booting with USB cable connected to a power source, it boots properly. A few moments after unplugging, it reboots, then bootloops. So...Bad battery? Even though it shows it as being at like 70/80 %?
Sounds like a bum battery... Had a similar issue with a S2.
Sent from my SM-T320 using XDA Premium HD app
You need to odin full stock firmware NK2.
Then evaluate battery.
Pp.