Related
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
I have had this problem for a while now. Whenever I shut down or reboot my nook it will reboot on its own over and over for quite some time.
It seems random, sometimes rebooting only a few times, but most of the time it reboots many, many times.
It'll get to the main screen, start loading stuff, then reboot.
I just recently figured out that if I turn the screen on and off rapidly for a few seconds it will interrupt whatever is causing it to reboot. But this does not always work.
I'm using cyanogen, and I think it started while using a nightly. I then tried a couple newer nightlies, then the stable 7.0, then newer nightlies, then the stable 7.1, and now the most current nightly.
Anyone have any idea what's going on? It's driving me nuts.
Could someone point me to a good tutorial on installing cyanogen, with how to format correctly and such? I would not mind starting from scratch with this, formatting it and everything.
Thanks so much.
Ok, first off are you running from an SD card? If so what is the brand and class?
Sent from space
No, its installed on internal memory. I do have an SD card that I use for storage, and its a Sandisk 16GB.
Well, I followed this guide: http://forum.xda-developers.com/showthread.php?t=1160424 and paid special attention to the partitioning section at the beginning because I have a blue dot version. I then installed the most current nightly of cyanogen and google apps. I also formatted /data a couple times and formatted /cache.
I did not get the rebooting problem.
Was it something to do with the partitioning?
And now its doing the reboot thing again. Just got most of my apps reinstalled and decided to reboot to see if it does it. And it does.
Any ideas?
Didn't know the root cause yet but first thought, could you redo the fresh installation, flash gapps but do not install any app. Try to reboot a few times to see if problem persisted. If not, thinking about what kind of app you installed.
That's what I figured I'd have to do. But first, I want to try to completely remove flash. I remember reading about flash causing rebooting somehow.
Anyone know how to get rid of all traces of flash? And adobe related stuff for that matter.
First off are you using beautiful Widgets? That causes a lot of problems. If that isn't it try installing your apps one by one and see what app it causing the problem.
Sent from my NookColor using Tapatalk
Not using beautiful widgets, but am using a few standalone ones. Bobclock d3, temp+cpu v2, text battery widget, and that power control one.
I uninstalled all downloaded apps, a couple to a few at a time. I got all the way down to just the basic google ones, nook tweaks, and a couple other ones I can't remember off hand.
At one point the endless reboot problem stopped.
So now I have started reinstalling apps one at a time, rebooting after each install. So far I have gmail, maps, market, nook tweaks, and youtube installed.
I will keep going through my list of apps, one at a time. It's a very time consuming ordeal, but gotta do it I guess.
I'm pretty sure it was nook tweaks. I reinstalled it and checked all the settings, and the rebooting stopped.
Not sure exactly what was wrong with it to be honest.
Anyone have any similar problems with nook tweaks?
Nook Tweaks may be causing my problem...
nookle said:
I'm pretty sure it was nook tweaks. I reinstalled it and checked all the settings, and the rebooting stopped.
Not sure exactly what was wrong with it to be honest.
Anyone have any similar problems with nook tweaks?
Click to expand...
Click to collapse
Apparently YES!
I have been having the same problem, random reboots. Not full boots, just a soft restart. And I dreaded having to actually do a full shutdown or reboot, because it would lead to a bunch of soft restarts. Drove me nuts.
This occurred on my original NC (old partitions, CM7 nightlies, stable and Mirage), and on my replacement one for a bad speaker (refurb has new partitions, Mirage with V6 and PDroid added).
So after reading this, I uninstalled Nook Tweaks and have been thrashing it for the last two days. Hallelujah! No reboots!
I no longer fear doing a shutdown and restart! Stability at last!
After a while, I'll probably reinstall Nook Tweaks to see what happens.
Thankyou, thankyou, thankyou for your post. Somehow, it never crossed my mind to think that Nook Tweaks might be the culprit.
Hi, I bought my GS4 two days ago and immediately rooted it via the motochopper method, and then installed ClockworkMod via the loki method. I then installed the then latest nightly (cm-10.1-20130530-NIGHTLY).
Now I understand that nightlies come with no promises of work, but I was just wondering if anyone else was experiencing a rebooting problem on their device. Mine reboots randomly, and often. Multiple times a day. On two occasions it has gotten itself into a reboot loop (starts rebooting, gets to the lock screen, and immediately starts rebooting), in which i needed to pull the battery. Still having the same issue on the May 31st build.
I'm just hoping that someone else has this issue, other then just me. Any ideas to fix it would be amazing!
Use a touchwiz rom, problem solved.
CM is nice for sure but, it seems to always be broken.
Fixed!!
After dealing with the issue for a few more days, it continued to get worse. I could no longer uninstall apps (every time I did it would reboot), and it became more frequent, even with updating to the most recent nightly every day.
I finally got fed up with it today. I did a complete wipe of data, cache, and dalvik cache, and reinstalled the latest nightly (cm-10.1-20130530-NIGHTLY). After installing gapps i turned it on and am no longer experiencing any issues!!! Even after i reinstalled all of my apps and restored the data using titanium. Hopefully it has fixed it completely, only time will tell over the next few days.
Hi,
I am reading from time to time here at xda about random reboots issue with ZUK Z1, so here is my short story.
I am the user of ZUK Z1 since last year at the time there was only COS12.1 and CM12.1 available. The phone was working great for the first few months, no single random reboot, even with heavy usage and tons of root tools like xposed framework, greenify (with exp. mode), amplify and other experimental tools etc. Rock solid stability, CM12.1, ZUI, COS12.1, no matter which one.
Some day, somewhere beetween feb/march this year I started to see occasional random reboots, sometimes once a week and sometimes three times a day. After the last one of this random reboots, the phone refused to boot. No recovery mode, no charging screen, no fastboot, even no access to qualcom recovery port for use with QPST and QFIL tools.
Tried to drain the battery and charge again with no success, tried to soft-restart by power button - no success. The thing that helped after phone sitting on desk for next three months, was to dissassembly the phone and reconnect battery. After this, the phone boots up again, bot the random reboot issue is back, no matter CM12.1, CM13 or COS12.1
And now the questions time:
The question is, is this a software issue after some of the updates or hardware issue?
Are there users with the random reboots problem with the newest firmware?
How to debug and catch this random reboot on the logs without ADB connected to see what is going on?
What have i done to fix the issue:
- reflash phone many times with different versions of COS12.1 and CM13
- flash fresh .zip from recovery
- flash directly from fastboot with official COS images the support page
- fsck, partirion check for errors, etc.
- formated phone by QFIL tools
- tried to track the problem from logs, but so far no value information are stored after reboot
What i am going to do:
- install ZUI 1.6 to verify that the issue comes back
- as much as i can, use the device with ADB logcat connected by cable, to catch the occasional reboot
- recompile kernel with enabled options to store crash reason after reboot ( kernel pstore feature or last_kmsg )
I am in the same situation as you, investigating....
Please update your results, very interested to find if software or hardware problems....
Thank you.
Carlos
Are you restoring apps after you flash your phone? If so, try not to. Just install basic apps you need and see if problem persists, since Google restores app with it's data.
Phone rebooted in recovery, so I think it's a hardware problem.
Phone is traveling to China again.
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Fenomen007 said:
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Click to expand...
Click to collapse
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
errecez1 said:
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
Click to expand...
Click to collapse
I love everything in that zuk so hope it won't brick. When it happen i will just chargeback money from gearbest
Hello,
I'm in the same situation !
My phone randomly reboots and also freeze (have to do an hard reset).
Have you find any solution ?
I am also having this issue... I will probably send it for the warranty. I have tried a few different roms, even restored back to CyanogenOS and the reboots continued...
I got mine since October, haven't had any reboots so far.
I'm running the latest update from cos without root or custom rom.
Seems like a hardware issue to me, I have tried everything software side.
same issue
I'm also having the same issue,any fixes??
Random reboots just stopped happening on my device a week ago. Before that I was trying different ROMs and flashed different versions of TWRP but the reboots were still happening. Then the reboots just stopped from happening and now everything is working perfect. I think it is a hardware fault. Probably some electronics (cables or what not) on my device are now having contact but were not having it before, I don't know. But if you are experiencing rebooting issues, just send your phone to the repair.
Any fix to this?
Whenever I do dirty flash, my zuk z1 random reboot twice a week. It is highly recommended to do a clean flash if you want to avoid random reboot.
Clean flash = No random reboots. @sebeqone
Hi all,
For the last 3/4 weeks my Moto X Style XT1572 has been randomly rebooting, usually this is when it is not in use and either in my pocket or desk.
I was running AICP and tried a couple of factory resets. This did not help.
I then factory reset and installed Dirty Unicorns (last weekly). Again this hasn't helped. No overclocking, undervolting, just stock kernels and I have tried handbag kernel.
Still rebooting.
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
rowlers said:
Hi all,
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
Click to expand...
Click to collapse
Flash the newest stock 6.0.1.
Without botloader, gpt, no oem commands(don't lock BL).
You need stock system to recognize: hardware or software problem.
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
I seem to have resolved the issue by using the Chill governor. Fingers crossed, but I've not had a reboot for 2 days now...
radon222 said:
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
Click to expand...
Click to collapse
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
JustLok said:
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
Click to expand...
Click to collapse
Moto X Style , Android 6.0 , Not rooted, pure stock, exact same symptoms as you guys with the random reboots while not in use , losing Bluetooth pairings... Did a factory reset, didn't change a thing. Sometimes, I can get 2 days without reboots, then have 2 in the same hour the next day. It sucks. I'm hoping the Nougat update will fix this, if it ever gets released for my version...
Got 1 doing the same stuff, all stock, gets warm, reboot itselfs, wrong date and time, and no bt pairing
Mine is still doing it too. Not as bad as it was but at least once per day, when idle, sleeping it just reboots for no apparent reason. Not ROM, Kernel and I have factory reset.