Help!!! Loaded phiremod on all 4 of our nooks yesterday, got them all tweeked and running great. I thought I adjusted the performance, per your recommendations, but looked today and they either reset or I didn’t do it. So I started doing them on all four. One on of them, as soon as I hit the Set on Boot, it locked up. It will boot, but it’s locked up and widgets all say problem loading widget. I tried rebooting through CWM thinking maybe it just needed a reset, but that hasn’t helped either. When powering off, I’m not getting the power off options, it just goes black. Any ideas??
Related
Hi guys,
I have an HTC Sapphire (HTC Magic from Vodafone UK). Problem with it this morning stopping me using it so urgently need some help!! I've included all details I can think of below to help someone diagnose the issue.
Been a very happy CM user for several months now and upgraded to 5.0.8 just a week or two ago. I did a full backup and wipe and haven't had any problems with it until last night.
Just before going to bed I noticed when pushing the menu/red button to turn the screen on, the keypad lights would light up but the screen wouldn't turn on. This happened a couple times in the last week but taking the battery out and restarting resolved it before. So I did that last night and it started up again and I went to sleep.
This morning I went to use the phone and it seemed a little strange, like some of my settings were back to default (security lock pattern went red when wrong, no battery % in title etc.), but the phone worked and I could make a call.
I then tried to configure the settings but as soon as I tried to enter any category I got FC's in the Settings app. So I restarted...(strangely silent/airplace modes weren't options, only reboot/switch off)
This time after the red Vodafone boot logo the phone got stuck in a boot loop - (CM specific: the 4-colour X swirl would be OK but after 3/4 silver X swirls the 4-colour one would start again) and this continues until pulling the battery out.
Left battery out a while but no help.
Went into recovery console and wiped cache - startup took a lot longer but still eventually got stuck in a restart loop.
Will reflashing CM help? Should I bother with a wipe (would rather not cause no backup!)
ANY OTHER IDEAS??? I'm really stuck/frustrated/depressed right now as this is my only phone and I'm not even living in my home country so am really cut off right now.
Thanks to anyone in advance.
Paul
I have never been able to get a tiamat kernel to work on my xoom. I followed a set of directions to completely start from scratch (again, plus formatted whole xoom 3-4 times before doing that) and flashed Tiamat ROM and it worked! I was even able to OC to 1.4, 1.5, then tried 1.7 which caused it to freeze and crash. Then it started acting funky so I did a restore and everything is fine until I turn the screen off or let it turn itself off with a timeout.
The system reboots into M screen and/or a black screen. A reset or two gets it rebooted. I increased the min freq and reset max to 1ghz. What can I do to fix this?? Thanks!
--- Update --- The browser causes a reboot as well. Random reboots into black screen. Def could use some help
ALWAYS stays on black screen when screen times out. Also does it after clearing data via honeycomb. Looking for a little help, can't post on the ROM thread yet
Well I would start from new wipe everything and reflash. Can't hurt. Sounds like something is broke. You can also try to fix promissions as well.
I've completely formatted the xoom including the sdcard and then started w/ 3.0.1 then did the 3.1 flash via CWR then the ROM install. The booting is better after complete wipe but screen still doesn't come back on after a time-out or i shut screen off manually. Browser also causes are boot which takes me to a 2-3 'M' reboot which then times out into black screen. 2 or 3 resets later and it boots up but then reboots within a couple minutes.
The official 3.1 update had my browser crashing which is why i said screw it, i'll flash new stuff. Could def use a hand
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Me as well I've tried everythingeverything. Currently on tiamat 1.1. With rc4 3.3.0
go into wifi settings and make sure your wifi disconnect policy is set to never
2JZ GZE said:
I am going through the same symptoms. Does anyone have any suggestions?
Random reboots and browser closes all of a sudden, no force close warning..
Click to expand...
Click to collapse
+1
also occassionally find the xoom stuck on motorola boot screen without me trying to turn off or back on..
Ill try but I don't think the wiring has anything to do with the black screen. This will lock even if wifif is off
Mine didnt like 1.7 either, I ended up leaving it sat next to a desk fan for a while to cool it down whioe switched off, then very quickly when it booted managed to get into antutu widget to drop the speed down and hit apply before it locked up again, rebooted all fine now, set it to 1.2ghz to be safe..
Kippui said:
go into wifi settings and make sure your wifi disconnect policy is set to never
Click to expand...
Click to collapse
Dude. I think this worked. I switched my wifi disconnect setting to, never while charging..it was set as, never(uses more battery power). I am currently on Tiamat 1.4.5 with CWM (rc4)3.2.0. Just let it chill over night and charge after a factory reset and viola. Have booted the screen in rotation and a few power offs. Even running at 1.2 g with set CPU. Been running smooth for 2 hours and I can't force it to even freeze. Could it really be that simple. Hahahah. Well see.
Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.
I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium
Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.
Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.
Good luck! hopefully the new one is error free.
I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr
Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.
Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.
Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...
Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.
My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.
gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.
I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium
I've been having some problems with my Galaxy S5 recently after ~2 years and some change of owning it. I'm stock rooted on the original ANCG KitKat version.
The problem: If I power off my phone, it will cause it to go into a bootloop, not going past the first screen (Samsung Galaxy S5, powered by android). I haven't found a reliable way to fix it from the loop, but I usually just remove the battery, wait, and try again until somehow it just works and boots up. This is extremely problematic because sometimes my battery runs out and after charging I'll have to go through this game of chance again until my phone works.
The next problem also adds to this frustration as well. When I attempt to pick up a call, my phone will sometimes just not work and restart itself. This leads to lots of confusion and I can't call them back for some time because the phone is stuck in a bootloop.
In the few times that I do get my phone to actually boot up, everything works fine except sometimes my Wifi just doesn't work. It gets stuck on "turning on" where the notification drawer quick setting icon is dim green and never gets to the turned on full green state, eventually just turning itself off (no green color).
I haven't done a factory reset or any real troubleshooting yet, as I'm a bit worried I won't even be able to boot up the phone and I don't have the time yet to spend a full day fixing it. Any help would be appreciated, thanks!
The calling problem may be caused by the google dialer app not being set as the the default phone app but as for the other issues i have no idea a factory reset is a good start though
unfortunately I had the same problem but I have marshmallow but the factory reset helped with the not booting up and see a big difference with the battery
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits