So, we keep coming back to our TF's and seeing that it has rebooted- has anyone seen a reboot, while the tf was on in their hands, doing something? Or is it safe to assume this is a sleep-related issue?
...just had my 1st random reboot. I was reading your scathing remarks in another thread and decided to look and see what my battery status was. It rebooted on the settings screen as I was setting it back down. On the bright side, it came right back up and is running fine.
I'm currently running [ROM/WIP][Unofficial] CyanogenMod 9 for TF101 and have only had the known issues in the OP. The script fix Tahl came up with for the MicroSD not mounting took care of the only one I really cared about.
Weird these RRs though, any thoughts?
Mine went through a random reboot while in my hands. This has happened once this whole time since ICS was released up to now. It has also randomly rebooted while sleeping at least twice.
Yes, it does seem to come back up, mine hangs on boot when it does, but I think that has something to do with being on the dock...yet I've tried manually rebooting while docked and closing the lid, and that doesn't make the device hang as it previously did on it's own RR at the boot animation.
But, speaking of which, I modified the old CMOS-style boot animation to reflect the ICS update..for both 16GB and 32 GB models
http://forum.xda-developers.com/showpost.php?p=23093227&postcount=9
I did have one reboot while in my hand with the stock rooted ICS ROM. With the Team Eos ROM i have had two instance of coming back to a tablet sick at the Eee screen. Reboot solved problems both time. will see how it goes tomorrow with a full night sleep.
FWIW. I also just installed Apex launcher work this ROM.
i did not have a reboot while holding my tf in hands so far, but i already had the case, that i found the tf hanging on bootscreen after obviously rebooting out of sleep mode...
...and as i have no dock, this does not seem to cause it.
luna_c666 said:
Yes, it does seem to come back up, mine hangs on boot when it does, but I think that has something to do with being on the dock...yet I've tried manually rebooting while docked and closing the lid, and that doesn't make the device hang as it previously did on it's own RR at the boot animation.
But, speaking of which, I modified the old CMOS-style boot animation to reflect the ICS update..for both 16GB and 32 GB models
http://forum.xda-developers.com/showpost.php?p=23093227&postcount=9
Click to expand...
Click to collapse
Now that you mention it, I had just installed my own custom boot animation (based on the TV show `Fringe`) - coincidence? Mine hasn't hung there though, it has always booted up completely...
Related
Damn this thing is buggy as hell. Can't wait for CM7 to be stable and useable, I really hope it kills all the bugs.
Yesterday i suffering from awful lag and unresponsiveness for some reason, I tried a shutdown, and it hung forever at the Goodbye screen. I did a battery pull, and when I booted up again it gave me a "Checking system settings...." message at the LG screen I had never seen before. After 10 minutes it booted up completely factory reset !
I was running stock ROM, rooted with the pre-dexopt patch.
So for next few days I'm just going to run the stock ROM rooted but without any apps or pre-dexopt patch just to see how it behaves.
This is definitely not as solid as my Nexus One, starting to wonder if I should have just gotten the Nexus S instead.
thats weird. yesterday morning i did a reboot with stock rom, and it showed me the same thing at start, but i guess it didnt feel the need to torture me because it just booted up like normal after that
Did you hold volume down while rebooting? That is what the stock recovery does.
I have had the phone for 1.5 weeks and it has froze or rebooted itself about 10 times.
Oh, and I am one of the ones with poor battery life also.
diablos991 said:
Did you hold volume down while rebooting? That is what the stock recovery does.
Click to expand...
Click to collapse
Nope i didn't. That's the strange thing.
This also happened to me. After outputting video to my tv, phone became laggy and shut it down. Turned on the phone without holding down any of the vol buttons and it said "system checking". Now it's stuck in a boot loop. Returning phone; this is my second phone. LG does not have great quality control.
The same thing happened to me. I turned the phone off and then turned it on and it reset itself. I started a thread on the LG forum about it.
http://www.lgforum.com/forum/boards/general/lg/topics/g2x-just-hard-reset-itself-for-no-reason
v8dreaming said:
The same thing happened to me. I turned the phone off and then turned it on and it reset itself. I started a thread on the LG forum about it.
http://www.lgforum.com/forum/boards/general/lg/topics/g2x-just-hard-reset-itself-for-no-reason
Click to expand...
Click to collapse
thanks for the link to the thread!
...
mapin0518 said:
Damn this thing is buggy as hell. Can't wait for CM7 to be stable and useable, I really hope it kills all the bugs.
Yesterday i suffering from awful lag and unresponsiveness for some reason, I tried a shutdown, and it hung forever at the Goodbye screen. I did a battery pull, and when I booted up again it gave me a "Checking system settings...." message at the LG screen I had never seen before. After 10 minutes it booted up completely factory reset !
I was running stock ROM, rooted with the pre-dexopt patch.
So for next few days I'm just going to run the stock ROM rooted but without any apps or pre-dexopt patch just to see how it behaves.
This is definitely not as solid as my Nexus One, starting to wonder if I should have just gotten the Nexus S instead.
Click to expand...
Click to collapse
Well there's your variable. Did you not see all the bugs popping up in that thread?.. Sure it certainly may not be that but to claim that the phone itself is buggy when there is clearly an outside variable affecting your system.
I more than less think that with all the bugs the g2x has straight from the box, what the pre-dexopt "patched" could very well be something LG was trying to cover up. Opening the floodgate to further problems (as reported in the pre-dexopt thread).
I just had a reboot and this time it gave me factory reset on my widgets....
mapin0518 said:
Damn this thing is buggy as hell. Can't wait for CM7 to be stable and useable, I really hope it kills all the bugs.
Yesterday i suffering from awful lag and unresponsiveness for some reason, I tried a shutdown, and it hung forever at the Goodbye screen. I did a battery pull, and when I booted up again it gave me a "Checking system settings...." message at the LG screen I had never seen before. After 10 minutes it booted up completely factory reset !
I had similar problems when I got my G2X, but installed LauncherPro, made it the default launcher, and Bingo, lagging and freezing gone. No problems since. Good Luck.
Click to expand...
Click to collapse
Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??
devilsxcrunner15 said:
Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??
Click to expand...
Click to collapse
Runner,
Sounds like similar to a few other user.
Something to do with the power button stuck or bad board.
Search user garen21. Read his thread..a few pages back. Gl
thanks man, ill give it a look. It's really out of no where that this happened.
There has been a lot of talk about the random reboots since ICS, but i have a slightly different problem. Since updating to ICS i've had a few random shutdowns....i think, it might be that it freezes with the screen off, i'm not sure which. ive never seen it happen when i was using it, the battery is never dead, i just try to turn the screen on and it won't. I have to hold the power button down for it to do either a reboot or a boot from scratch not sure what it is.
here is what i have
- stock transformer (rooted in HC to fix left speaker volume)
- upgraded via ota to ICS (seemed to work correctly)
- not overclocked
- no other hacks
- haven't done factory reset (don't want to, but might if it keeps happening)
Has anyone else seen this since ICS ??
I haven't had that problem but I've had a lot of others from bootlooped, to the whole tablet freeze... I'm on stock ics and factory reset didn't help what so ever........
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1518552
nonoheran said:
http://forum.xda-developers.com/showthread.php?t=1518552
Click to expand...
Click to collapse
I started to read through that thread (lots of pages there), i didn't notice anyone with the random shutdown on there that's why i started this thread, just in case it started happening to other people too.
I will try some of the suggestions on there to see if it goes away.
Same issue here - it is either freezing while the screen is off or shutting down. Only way to get it to respond afterwards is to press and hold the power for 10+ seconds, release, and then again for 5+ to turn it back on.
I've reset to defaults with no success. Running stock rooted ICS.
Same issue!
I've noticed this happening on my tablet too.
Mines completely stock in every way, never rooted or modified in any way from stock.
After the ICS update I've noticed that... probably once a week or so I'll go to turn on my tablet only to find that it's essentially turned off.
There was plenty of battery, and no obvious rhyme or reason for the shut down ?!?!
Same here. Stock TF101, after ICS upgrade device doesn't respond to wake button. Plenty of battery. You have to hold the button for a way longer than just a power on press.
I've started having the same issue after updating to ICS. Sometimes it's random reboots and other times I'm getting this shutdown issue.
I have this problem too.
I try to fix this by changing the ROM but all still get this problem.
Stock ---> RevolutionHD ---> EOS with cornerstone 4
I have had same problem with the random reboot/boot loop problem with ICS and I have tried stock unrooted / stock rooted / Revolver / RevolutionHD. All do the same thing. If I have the screen off for extended periods of time, it reboots and gets caught in a boot loop. The 10+ then 5+ button hold works to get it restarted. I am trying different apps to see if one is the cause. Most of the time I seem to remember that I was browsing just before shutting the screen off.
Will let you know if I narrow this down as I have multiple browsers installed. Note: I mainly use Chrome and FireFox Beta the most, will try removing those and testing.
Sent from my HTC MikEVO
Same here, having random shutdowns and sometimes when I lock my screen it restarts and get stuck at the bootanimation.
Also it often reboots when I use Splashtop remote. It works well, then I touch the screen and it restarts...
I hope Asus will fix this as soon as possible, but i think it will take a while.
I believe this has to do with the power management issue. I've noticed that after being unplugged from the power supply. The tablet will stay on. Once when the power level dips below a certain percent, the tablet automatically shuts down. When it reboots, sometimes the wheel will stay stuck. The only way to keep the tablet powered on is to have the cable plugged in. That defeats the purpose of a portable tablet, might as well get a EP121 then.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Hello,
I recently changed the LCD of a S6 edge. I installed it and turned it on and it booted up fine. I went to make sure everything was working. While I was playing music it would restart. I thought it was odd, so i was waited til it came back on and started using other apps. Same thing..restart. So, i booted to safe mode. Same thing...restart.
So, I tried factory resetting. After that, it would just get stuck in a endless restart loop cycle.
I have also tried reinstalling the OS using Odin. I ran Odin and it said everything passed. The phone restarts and goes to installing updates.
It gets to 32% every time then it says "erasing". After a few seconds of displaying "erasing" it just starts its endless reboot cycle again.
**EDIT: I should add that it never restarts when it's in the download manger.** So, that makes me think its a OS issue.
*EDIT#2: This is a good video. I did all of this. Got to the 9 minute mark and where his comes on, mine restarts again.
Any help?
Thank you!
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
3mel said:
back in the latter days of flashing S4 custom roms there would be the occasional user who couldn't boot and it turned out that there was some detail in the roms that didn't work with some 3rd party LCD screens.
check the reviews for what you bought and see if you are alone or not.
the issue with those screens was fixed by the devs so if nothing else you might be able to go custom with it.
Click to expand...
Click to collapse
Hi,
thank you for your reply. I learned about all of this last night lol. so, i'm not exactly sure what you mean. I bought the LCD+frame from Ebay. It stated it was pulled from a working unit.
Could a bad battery cause all these issues? I notice when i power down (only way I can power down is if I Hold POWER+VOL DOWN and select power down) that the LED light stays on.
Hello, could someone delete this thread. I have posted a more detailed thread on this issue.
if it says it's an LCD screen it's not an original part. my point was that some people have had issues booting up roms because of screens.
that was something that was fixed in custom roms though so if you can't another solution a custom rom that works with 3rd party LCD displays might be an option to consider.