I know I might have to pull the battery....I downloaded ROM manager in the hopes that it would be an easier way than spending a couple hours upgrading to CM 6 from my older version of CM (I don't recall which version it was).
DLed CM6 via ROM Manager as well as the google apps. It asked to reboot to complete install, I chose not to wipe data, and currently it's stuck on a screen showing the date as Sept 2 2008 and with stripes of red, green, blue, and white going across the screen. Display is not changing, nor does it seem do be responding to key presses.
Advice please? Anyone else gone through this?
[EDIT]
Pulled the battery, it was stuck in a boot loop. I started walking to the T-Mobile store to get a Samsung Galaxy. After a while in the store, I heard a text message notification from my phone. The boot loop had damn near killed the battery, but it booted. Now going to try it the right way by following the Froyo update guide that I was in too much of a hurry to see earlier.
Still want a Galaxy though
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
HoochieCoo said:
Since this morning, when I boot it will get stuck on that red eye screen. I've waited several minutes and it won't go on.
So I end up pulling the battery and usually that works. Sometimes I have to do this twice.
Not sure how to even diagnose this.
Click to expand...
Click to collapse
Are you rooted or completely stock?
Sent from my ADR6300 using XDA App
Rooted. I just tried restoring a backup from 3 days ago and had the same problem. So I restored back to the latest. When it finally does boot, it seems to run great.
I have a backup from further back, just not sure it will make a difference. Might give that so shot too.
I really think it is booting all the way, and just doesn't stop displaying the boot animation.
The reason I think that is because at some point the power button makes the screen go on and off, and there is haptic feedback in the same places where my lock screen tabs are.
At any rate, and this sounds unbelievable, but I pulled the sd card out and it booted normally. I put the card back in, and now it seems to boot normally. Can't explain it.
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
Guys, I don't usually post on forums but now I just can't make myself sending it back without making sense of this first.
So I got the Nexus 7 one month ago, barely used it and didn't install any fancy stuff on it. One week ago I saw an app that I wanted and before installing it I had to install BusyBox. In my foolishness I didn't read the description that the tablet has to be rooted before I install it.
When the installation finished this exact problem suddenly happened: youtube.com/watch?v=5d319gUeYLM
Why I'm determined it's a hardware problem:
- The next morning I turned it on and everything was back to normal, however, after 15 seconds it slowly dimmed and got back to that exact screen
- You can navigate the menus and hear the sounds
- The morning after again, back to normal, I hurried and did a factory reset and deleted everything. This didn't help at all, the problem was still there and the screen never went back to normal even for a few seconds.
- It keeps the same lines in the recovery menu and on boot.
While everything points it's a hardware problem and the guy on YouTube said Asus replaced his display, how can this simply be a COINCIDENCE? For this to happen exactly when I installed something it wasn't supposed to be installed if the tablet wasn't rooted?
64GB OnePlus Two running OxygenOS.
Backstory of the last time this happened:
A while back, I was on Snapchat when all the sudden my phone just froze. Didn't think it was anything special since it does that not too infrequently, but then the screen went black. Again, wasn't too concerned because it has done that before as well.
It began to reboot as normal, but right when it got to the final stage of the boot animation it froze and rebooted. This time it stopped toward the beginning the the animation and rebooted. On the third boot attempt, it showed the "optimizing apps" message like the Dalvik cache had been wiped. Again, up to this point it was nothing new (I had crazy problems with the latest OxygenOS before I rolled back to 2.2.0) so I wasn't horribly concerned.
But at about 120/160 optimized, it froze on that screen and crashed. And that's where I am right now. No matter how long I hold down any combination of buttons, the screen will not come on and it fails to otherwise respond, with two exceptions.
I tried the hard brick recovery method, but no amount of holding volume up would get it to show up in device manager.
When I went to bed last night I decided to give it one last shot. Held down the power button for a sec, and it vibrated and then powered on. Went through the whole "optimizing apps" routine and started up just fine. It was reallllly sluggish and laggy for a few minutes but now seems to work fine. Only thing I can guess is leaving it plugged in for a few hours had some effect. Oddly enough, it was at 98% to start and was plugged in doing nothing (that I could tell) for a few hours, but only showed 86% when it booted.
Well, it happened again. When it happened the last time, I rolled back from OxygenOS 2.2.1 to 2.2.0 since that seemed to be the only change I had made recently. I'd left it stock till now, but I decided I wanted root and Xposed so I flashed TWRP 3.0.2, SuperSU 3.65, and Xposed. When it rebooted after this, it froze during boot and shut off. Now it won't do anything. Holding volume up won't make it show up in device manager on my computer for the hard brick recovery, and leaving it plugged in for ~20 hours didn't help either.
Please help! I'm an extremely busy engineering student and finals are just about a week away followed by flying home. I really need to fix this ASAP.
Okay, I remembered that my phone sometimes reboots when it's dropped/set down sharply, so I rapped it a few good ones on the desk. And it booted. I'm thinking there's a loose connection inside? Should I RMA it?
Guess I spoke too soon. Froze and crashed again while booting.