I've been trying for a while now to get my TF101 re-encrypted since I went to Custom ROMs, with no success. I even went as far to go back to stock non-rooted ROM (applying the updates one-by-one like you're suppose to) and it's *still* either rebooting or doing nothing when I select "Encrypt Tablet". Specifically:
Stock 9.2.1.11 - Reboots immediately.
Stock 9.2.1.27 (Latest) - Reboots immediately.
Android HD Revolution - Reboots immediately.
CM10.1 Nightlies - Sits there with the little Android logo, doing nothing.
CM10.2 Nightlies - Same as above.
KatKiss (Latest) - Reboots immediately.
In all cases, the tablet is not successfully encrypted. I guess my next step would be to go back to an even older ROM, such as CM 9.x series. And if that doesn't work, I probably have some nandroids laying around (I always make a nandroid backup).
generalmx said:
I've been trying for a while now to get my TF101 re-encrypted since I went to Custom ROMs, with no success. I even went as far to go back to stock non-rooted ROM (applying the updates one-by-one like you're suppose to) and it's *still* either rebooting or doing nothing when I select "Encrypt Tablet". Specifically:
Stock 9.2.1.11 - Reboots immediately.
Stock 9.2.1.27 (Latest) - Reboots immediately.
Android HD Revolution - Reboots immediately.
CM10.1 Nightlies - Sits there with the little Android logo, doing nothing.
CM10.2 Nightlies - Same as above.
KatKiss (Latest) - Reboots immediately.
In all cases, the tablet is not successfully encrypted. I guess my next step would be to go back to an even older ROM, such as CM 9.x series. And if that doesn't work, I probably have some nandroids laying around (I always make a nandroid backup).
Click to expand...
Click to collapse
I have logged this issue via bugreport (logcat) for OMNI as well as I experience the same on my Samsung S3 with CM and OMNI. I do not seem to get any answer except it should work. This is becoming a big issue for me personally as I am required to encrypt my phone if I store company e-mail.
I also noticed that with custom ROMs (e.g. OMNI) there is no multi user support although this is clearly a 4.3 and higher basic function. Security on the custom ROMs are reduced it seems ...
Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
Device: SM-G920I
ROM name: Xtrestolite 3.2
ROM version and base: G20IDVU3EPC3
Build number: XtreStoLite Deo Mod v.3.2. DPD8
kernel version and its settings: Stock Kernel
Rooted
Problem:
Every now and then, my phone will just become non responsive and automatically restart on its' own. I have had this problem quite a lot on different versions of this ROM. I do not have Xposed installed as this would cause my device to constantly overheat and make the restarts worse. The restarts are intermittent and i have no way to diagnose the reason. At least once a week, it will restart and then the optimising screen apps come up (as if I had just flashed something). I do have lucky installed, but the problems occured before this. The restarst are more noticable when I use the app headspace, it's a meditation app so I will know that the phone restarts because the audio cuts out. Any help would be appreciated.
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
User422 said:
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in the rom threads to see if anyone else is having the same issues ? Unfortunately using cm/lineage based roms can have bugs as they are not based on samsung firmware
Regards
Sawdoctor
Hi, thanks for the answer. I wanted to say that I went down to resurrection remix Rom which is based on Android 6 (Marshmallow).
It's fine now.
Now I'm just looking to find a way to hide my root. Can't use my banking app anymore since I've rooted my device.
Update 2: The phone problems I have described reoccur over and over again. A factory reset via TWRP fixes that and then the phone slowly goes back to the old problems.
I don't know what to do anymore except for doing this over and over again.