On every ROM I flash, except CM12, the setup wizard crashes where it asks for my name to personalize apps.
I'm doing clean wipes each time. I've tried different gapps, putting my name in, not putting my name in and I'm out of ideas. CM doesn't even have the step where it appears to be crashing every time.
Any help would be appreciated. I'm using twrp.
Well, I kind of figured it out on my own. Googled it and found information concerning similar issues several years ago, different builds and different handsets, but each had the same cause. An issue in the GApps.
I flashed the ROM independently and rebooted. After the ROM booted up the first time, I rebooted into twrp and flashed GApps.
I had issues updating until I got to WiFi, but my phone worked. I'm going to try some different things now that I'm on WiFi, and will update.
Related
Hey there!
Sorry for creating a pull for asking help first, but I've been messing around the forum and Google with no results.
The thing is: I have a Motola Moto G 2013, it works pretty fine. Some time ago I'd like to try CM 12.0, and everything went okay. I didn't need to install the GApps cause, don't know why, it already has Play Store and Google Services, so, no problem.
Some days ago my phone started to work PRETTY bad, and reading in the web found that CM 12.1 were released, so i thought "lets give it a try"
CM 12.1 installed well, but without any GApp, so started to search the GApps packages. Tried with many of them, Pico, Nano, Stock, from april of this year, may of thies year, even from july this year! But none of them worked. When Android starts (after GApps install) appears a windows that says that a factory reset is needed. After that, starts the nightmare. Constantly, really constantly, appears two windows "Play Store has stopped" and "com.google.process.gapps has stopped" and after that, like pressing the "Ok" button10 or 15 times, almost every time, it gets on black and only can power off and restart,
As I could, went to settings > all > and cleaned and stopped every google service. When I made that the device perdormance goes pretty much better, but when try to acces mi gmail o opening play store, again, the same.
I thought that changing the recovery would do some change effect. Tried with CWM (the one i had from before), Philz Touch and now the latest version of TWRP (the one that looks like Material Design), with no effects. And finally, tried with other ROM. I downloaded AOSP http://forum.xda-developers.com/moto-g/development/rom-android-source-project-t3060704 but again, gapps error. Also tried with blisspop, but couldn't install it, it was like 4 a.m. and my mood wasn't good for keep trying.
Before you ask, yes, I made every goddamn wipe before and after the install (after only dalvik and cache partition)
It's like no matter what ROM, no matter what version of GApps, the doesn't work. I've been like this from two days ago, and really, the different options are starting to vanish.
Sorry again for creating a topic for this, but is this, or throwing the PC and mobile above the window.
And, also, sorry about my english, I'm from Argentina.
If you need more details, like Recovery versions, GApps versions, screens, anything, ask 4 it.
Cheers and thanks!
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.
I've followed each step for every ROM including flashing the needed recoveries or nightlies
For sometime I'm having these bootloop problems I ignored it at first thinking Incompatibility with certain ROM's but now I noticed that its happening a lot
ROM's that currently work
Official CM 12.1 Nightly that im on now.
http://download.cyanogenmod.com/?device=bacon
Exodus
http://forum.xda-developers.com/one...om-kernel-sultanxdas-cyanogenmod-caf-t3199862
This is the one I was on before and went to
Sultan's With F2FS
http://forum.xda-developers.com/one...om-kernel-sultanxdas-cyanogenmod-caf-t3199862
I had root troubles so I flashed NuclearSlim and got stuck in a boot loop tried all things(Wipes,recovery flashing even installing latest nightlies) nothing worked
ROM's that used to work but don't anymore
Reserruction Remix
http://forum.xda-developers.com/oneplus-one/development/rom-resurrection-remix-lp-5-2-0-t2971715
NulclearSlim
http://forum.xda-developers.com/oneplus-one/development/nuclearslim-t3133741
ROM's that didnt work
Even though Sultan's ROM with F2FS one worked, this one didn't after which I finally had to go to official nightlies
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-12-1-t3120259
So, I'm just trying to figure out the problem here before I waste more time downloading other ROM's just to get stuck in bootloop.
No replies ?
1. Check your firmware (it should be good but still check it)
2. Try Clean Flash
3. Flash ROMs over CM12.1 Nightlies ...
4. Try flashing stock ROMs via fastboot (eg. COS12.1 or 44S) and then start from scratch...
4th Option always works for me ..
I always do Clean flash Maybe I'll try 4th option this time. Its the Restoring the backup afterwards that annoys me
I've been stuck in a bootloop for several weeks now and have been unable to recover from it. In my case, I've tried flashing every version of the the stock ROM, and many CM variants, but with no success. To me the problem reminds me of an issue many of us have had with our old HTC HD2s where over time memory cells in the NAND would eventually go bad. If the bad area of the NAND happens to reside in the system partition then any time data is written there a bootloop results. We were able to work around this on the HD2 by savvy developers that created partitioning tools that were embedded in recoveries which allowed users to remap their NANDs so that the system partition could be placed in healthier section of the NAND. Unfortunately, there seems to be no such tools with the OPO.
Other folks seem to be having similar problems with other partitions. For example, on my second OPO flashing TWRP-2.8.6.0 always results in the device being unable to boot into recovery, but other versions have no issue (several other users have mentioned this too).
If my theory about this is correct what is happening to you is certain ROMs are of a size where no critical files are installed in the damaged section of your NAND, where other ROMs place files there causing corruption and ensuing bootloops. In my case the damaged portion must reside at the beginning of the /system partition so that any ROM I flash causes the bootloop.
Your reply made me both sad and Satisfied. Sad cos of the reason and satisfied that I at least got some reason. Thank you.
I've had a strange issue with my LG V20 ever since I got in last year and installed LineageOS 18.1 after rooting my H990 on LG firmware 10d (H990ds10d_00_OPEN_AU_DS_OP_1216.kdz) with DirtySanta and installing TWRP. Whenever I left the range of my Wi-Fi network, I would cause the System UI to become unresponsive while doing certain tasks - Unlocking, going to Settings -> Wi-Fi, expanding the Wi-Fi quick toggle in notifications, and probably a few more things.
This doesn't happen on the aforementioned stock firmware, nor on 10g AU 0117 stock firmware either.
For a while, I dealt with it by simply not using Wi-Fi. This sucked because I couldn't access computers over LAN, mobile data was slower, and it also had a data cap that I had to be wary of.
However, I decided I wanted to fix it.
I saw some recommendations involving installing every Lineage version since 14.1 sequentially until the latest. This didn't make sense to me, as clean flashing shouldn't leave any remnants behind, but dirty flashing that many versions went against everything I'd ever heard of regarding custom ROMs.
I also heard that it could be a modem firmware issue. Since I started on the last version of the stock OS for my region vulnerable to DirtySanta I thought surely not.
I later found out about KDZWriter, and used that to install the latest Nougat version of the stock rom available (also mentioned above). After installing that, I tried installing the latest LOS on top, which constantly informed me that com.android.media had stopped, I still had the LG sounds and wallpapers, and I didn't go through the initial setup - A sign of a dirty flash. I was still crashing in the same way too.
I formatted my data partition in TWRP (the "type yes to confirm" way), and tried again. Same crashes.
I've been awake for a little too long trying to fix this, but :
What I believe ended up working was backing up my /efs and /firmware partitions in TWRP while on rooted 10g firmware, dirty flashing LOS on top, formatting data as before, then flashing my /firmware backup in TWRP.
I'm hoping for this thread to document this issue as well as the fixes that worked for people. I saw tidbits of information spread out everywhere, so I'd like a central repository for it.
I hope this caffeine-induced writeup will help someone else with the same or similar issues.
If I have any more experiences with it, I'll do my best to write them down. Please share your experiences too!
Hi all,
Installing a custom rom on an XZ Premium; it's my first time dealing with this so its possible I missed something. I successfully installed TWRP and adb sideloaded the most recent Cherish OS rom. I was able to set up the phone with no issue, but upon rebooting for the first time back into system, it hits the boot logo, which animates correctly, but then hangs there indefinitely. I have wiped system memory, reformatted, and reinstalled, and the issue persists. I have also tried other ROMs. Arrow had the same issue, as did the Pixel experience, which leads me to believe that it's not an issue with the rom, but something with how I have configured the set-up.
I looked around for solution, but wasn't able to find much on the specific issue of only having issues on second boot, rather than initial. Any help would be appreciated.
I think your TWRP version is the Problem... (I think there were a lot of complaints about 3.3.?.? and higher) I had a similar Problem; TWRP wanted to use /data and if i formated the device, it would endless bootloop (I think because of the encryption the OS uses by default) So i decided to flash a older version (were this wasn't a problem) and I picked twrp-3.2.2-0-maple.img (maple because i have single SIM variant) and I didn't even needed to format the device and it still works (after i flashed Magisk and some other stuff/ "enhancements", that don't impact he OS) and everything still works smootly.
Maybe you should just flash a older version of TWRP (like 3.2.2-0) But i can't guarrantee, that it'll work on Pie(since i don't have it).