Related
I've been experiencing random reboots since I bought my Developer Edition but today I think it hit me real hard with the random reboots in short intervals.
this kind of reboots happened to me both on completely stock and custom rom but today heavy reboots occurred when I was on Insert Coin 2.0.3 (S-Off).
According to someone's advice, I installed catlog and try to record the events until the phone reboots. So I post my logs here and hope some one could save me from this misery.
the first file was recorded with "write to disk every 200 lines" so it may miss some very last event when phone rebooted. The next ones were recorded with "write to disk every 100, 20 and 10 lines". I hope some devs could have a clue on what is happening with my phone.
I also save the log file AFTER phone reboot but they were too big to attach. If you think those might helo, I'll post them somewhere else.
Might be something to do with Xposed
BenPope said:
Might be something to do with Xposed
Click to expand...
Click to collapse
Yeah, I've noticed that some custom ROMs got issues with Xposed on S-Off device. However, as I mentioned earlier, this happened to me while I was on completely stock rom, too.
I've made a few observations and found out that I haven't got a single reboot on AOSP for a whole day but AOKP still gave me random reboots (not as frequent as on InsertCoin but still).
Any help would be very appreciated
might be worth trying to install sense rom again stock or custom and do full wipe, cache and dalvik. strange that an aosp rom works fine. must be something caused by a sense rom, drivers or framework. was this problem introduced when you started using 4.2.2 roms? have you updated to the new firmware.zip?
well, my habit of installing new roms is always do a full wipe so I think the cause of reboot should not be related to that.
After getting no reboot on AOSP roms (carbon, cm 10.1), I decided to go back on custom sense roms but no luck. reboots just came back no matter what roms I was on (renovate rev 45, insertcoin rev36, rayglobe 4.3).
I went to stock again with RUU dev edition (.16 one). Phone gave me a reboot right after I finished setting up (as new phone). However, it has been running stable up to now (3 hours).
Should the reboot have any thing to do with Sense, i'm wondering. I would be very thankful if any devs can help me on this issue. I'm willing to make as many logs as required or install any custom, stock roms if neccessary.
Sincere
Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?
thex2 said:
Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?
Click to expand...
Click to collapse
I'm going to answer your second question first, as the second answer shapes the first answer.
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
The conflict will happen due to system settings.. All system settings go in /data/data along with your user app settings. Most settings will go in an sqlite database.
The boot loop problem occurs usually when there is an entry in one or more of these databases that correlates with a setting that no longer exists, or the entry doesn't match the options in a ROM. For example, if your ROM allows you to set screen sleep in 15, 30, 60 seconds only, but your database has your setting set at 45, android doesn't know what to do and boot loops.*
The fix is of course, wiping data.. This is why when restoring using titanium backup on a new ROM, we recommend only restring your user apps and data (using the filters and options) otherwise if you restore system apps and data you're restoring the problem.
The first question, you can restore app a from a nandroid backup using titanium. There is an option in preferences.
*please note, this is just a basic example for illustration purposes. Screen sleep may or may not cause a loop
Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
rootSU said:
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
Click to expand...
Click to collapse
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?
thex2 said:
Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
Click to expand...
Click to collapse
Let's see what I can do
thex2 said:
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Click to expand...
Click to collapse
There are no hard and fast rules.. If you're going from Dev A ROM to Dev B ROM, you will almost certainly have to wipe. Also, between major version updates (5.0 to 5.1 for example) you too will most likely have to wipe
Usually for any upgrade on the same ROM that isn't a major version update (dev a 5.0 to dev a 5.0 base) you usually won't have to wipe, but you may well have to, depending on whether the dev changes things a lot. Always have a titanium and a nandroid backup before updating.
thex2 said:
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Click to expand...
Click to collapse
Yes probably. Restore the full nandroid if you want.
thex2 said:
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Click to expand...
Click to collapse
It depends which launcher you're using.. If you install a launcher from play store, it is a user app.. So if you're restoring user also using titanium filters, it should restore it fully, including widgets etc. That said, sometimes it doesn't always work out. If the launcher has built in backup, it may be wise to use it.
If the launcher is built into the ROM, its classed as a system app, so even though user apps and system apps both keep their app data in /data/data, it will not be seen with titanium if you're using a filter to shoe only user apps and data.. Work around is backup system and user data without a filter in titanium then when restoring, apply the filter for user apps.. Then once user apps are restored, find the system apps you need to restore data for and restore individually as required. You need to restore as little as possible though to avoid the boot loop.
thex2 said:
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?
Click to expand...
Click to collapse
Usually not.. Generally ROM v2 changes from ROM v1.. ROM v3 is usually even further away from ROM v1. If a dev is changing such a setting they are probably doing so for a reason.. Sometimes if the setting is part of a function that the dev decides to remove again ROM v3, its possible. But its best to be prepared and accept that wiping and restoring is a common practice in custom ROM flashing
I've searched and read through ten page threads and still haven't found an answer to this. I am on stock deodex lollipop. I set up fingerprint lock screen perfectly fine and made a backup of the ROM in TWRP. I had to restore back to that backup but now fingerprint lock screen isn't working. I had to flash a zip via TWRP to disable the lock screen, thank you dev who made that, and now I'm in the same boat as those of you who posted that fallback password does not let you disable fingerprint lock screen. The phone will not read my fingerprint at all, it doesn't recognize it. I've made sure that I'm on the COD6 baseband. I don't know what else to do.
Whenever it's troubled me I Odin to stock + factory reset.
Have you tried the things these guys say
http://forum.xda-developers.com/showthread.php?t=2919478
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
I think it's don't configure it til you're rom'd up.
Never back up your rom or restore a backup that has fingerprint stored, always delete the fingerprints before making a backup or wiping to flash a rom!
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.
Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.
So I should not worry about flashing the new 32r radio?
shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect
Hey there simbo, what do you say about flashing the radio?
Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.
roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important
roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.
Hi everybody,
at the moment I have a big problem. For about 3 weeks I bought a Mi5 pro.
I have spent about 2 weeks reading about the possibility to become root. So first unlock the bootloader (is already done), installed MIUI 8.0.2.0 stable global with MyFlash and after that, installed root (SuperSU) with temporary TWRP. I have done this way: http://en.miui.com/thread-309596-1-1.html
Everything went good. But I have massive problems with bluetooth. There are many threads in the net about bluetooth and MIUI, it seems to be a old case.
I have read here ( https://xiaomi.eu/community/threads/smart-unlock-and-bluetooth-problem.32703/ ) that the problems with bluetooth come from MIUI. Because of that (and a little too because I dont like MIUI), I thought, that Cyanogenmod could be a chance. In first case for the bluetooth problem and in second case, because I like it.
Now I have a few questions about it.
I know how to install TWRP and this is not a problem. And install Cyanogenmod is really very simple.
1. If I install Cyanogenmod with TWRP, do I loose the unblocked bootloader?
2. If I want to go back to MIUI (dont hoppe that), because I have massive problems, can I make a full backup of my MIUI system now and later recover all like it was? Like Acronis TrueImage in Windows? And if it possible, how much about place does it take? I dont have many files likes videos or fotos. Just the system with some apps.
3. If I make backups from my apps in MIUI now with Titanium Backup (apps, settings, files), can I recover them later with Cyanogenmod? Or is something incompatible (some strings in the system or something like that)?
4. I really need root. Is there a version of Cyanogenmod with root or a simple way to do it in Cyanogenmod?
5. Is there a way to obtain OTA updates with a rooted phone from Cyanogenmod? Or every time I have to flash the whole firmware? In that case, the danger that something dont runs like it should is high.
6. Do you think I should give Cyanogenmod a try about the bluetooth problem or is it hopeless, because Cyanogenmod is based on MIUI?
I would be thankfull for every little help.
Regards.
1 - no
2- yes, backup will take max 3.3GB space (boot, data, system)
3- you can try restore them, if there will be some problem/force close just install app from play store
4- Settings -> About phone -> tap 8 times on "build number" -> this will enable Developer options. Now go to settings -> developer options -> Root access -> select what you want
5- If your phone is official supported by Cyanogenmod yes, check this website for you device: https://download.cyanogenmod.org/ If you find some UNOFFICIAL builds, you have to download full zip put on SD card and flash using TWRP. There is also UNOFFICIAL CM13 ROM with OTA update: http://forum.xda-developers.com/mi-5/development/unofficial-private-cyanogenmod-13-builds-t3426349
6- Cyanogen mod is NOT based on MIUI
veimus said:
1 - no
4- Settings -> About phone -> tap 8 times on "build number" -> this will enable Developer options. Now go to settings -> developer options -> Root access -> select what you want
Click to expand...
Click to collapse
Wow, that is what I name EASY!
But you say it is not based in MUIU, but what about that? http://forum.xda-developers.com/showpost.php?p=68597884&postcount=23
The talk about kernel sources, but is the same company. Maybe the bluetooth error is also in the kernel? What I dont hoppe.
And I read, that some users have problems installing CM13 with MIUI 8 installed, and that it is better to go back to MIUI 7 before installing CM13. Can anybody confirm this?
One last question: I would make a backup with twrp before. But everywhere I read, that it is better to that in a sd card. But my Mi5 pro dont have this. Is there a problem with this or is the backup in a safe place, even after I have installed CM13?
xdaerdeve said:
Wow, that is what I name EASY!
But you say it is not based in MUIU, but what about that? http://forum.xda-developers.com/showpost.php?p=68597884&postcount=23
The talk about kernel sources, but is the same company. Maybe the bluetooth error is also in the kernel? What I dont hoppe.
Click to expand...
Click to collapse
Xiaomi - company name (they release kernel source)
MIUI - system based on Android
Xiaomi released kernel source code so developers now they can build custom ROM, and for official CM support kernel source code are required With source code now they can even fix Bluetooth error- its impossible without source code. It's like application in Windows, you cant fix something inside that app if you don't have source code :]
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
xdaerdeve said:
And I read, that some users have problems installing CM13 with MIUI 8 installed, and that it is better to go back to MIUI 7 before installing CM13. Can anybody confirm this?
Click to expand...
Click to collapse
I always do a full wipe formatting system partition in TWRP and never had problem instaling CM13
---------- Post added at 08:19 PM ---------- Previous post was at 08:16 PM ----------
xdaerdeve said:
One last question: I would make a backup with twrp before. But everywhere I read, that it is better to that in a sd card. But my Mi5 pro dont have this. Is there a problem with this or is the backup in a safe place, even after I have installed CM13?
Click to expand...
Click to collapse
i have OTG adapter and I keep backup in USB stick like this one: http://www.ebay.ie/itm/VENTION-USB3...dapter-Converter-OTG-For-Phones-/172266246233
veimus said:
i have OTG adapter and I keep backup in USB stick like this one: http://www.ebay.ie/itm/VENTION-USB3...dapter-Converter-OTG-For-Phones-/172266246233
Click to expand...
Click to collapse
That means, I need something like that or can I make a backup in the phone storage? Maybe does TWRP does this in a safe place of the storage? Or does it go lost, when I install CM13?
I am ready. Everything gone good
Is it possible to change the key to go back and recents apps? For years I work with the key to go back at the right side and the key for menu on the left side. In CM is the other way round.
And I dont want to use the softkeys, I want to use the hardkeys from my Mi5 (more display available).
Thanks in forward.
i have solved the audio via headphone in cm13 for mi5, but as i m not eligible to reply post in the rom forum, so everyone can't enjoy it
---------- Post added at 01:21 PM ---------- Previous post was at 01:19 PM ----------
main problem of cm13 is now VolTE