Issues flashing CM nightlies - Nexus 10 Q&A, Help & Troubleshooting

Hi guys,
Im currently running CM 10.1-2013072 Nightly and any time I try to update via OTA my tablet starts freaking out. all the latest versions are 10.2. The Stock keyboard repeatedly force closes. Apps that were installed prior to the update are no longer installed. I have tried doing a full wipe (factory, cache, system) then install the latest nightly. It installs fine but when It loads up to the initial configuration screen the stock keyboard repeatedly ForceCloses still and I cant do anything with the tablet. I have gapps-20130301.....is there a newer one or is this still the latest gapps? Thanks!
UPDATE: I was using the wrong gapps version. All is good now

Related

[Q] 4.2.2 random reboot!

Mysterious AOKP 4.2.2 rom, Feb 22 build, faux 123 kernel, .33 radio, twrp. Took a pic, decided to take another one, hit the shutter, the phone froze, and then rebooted. downloaded some apps from the play store, rebooted on its own.
I haven't had any problems with stock 4.2.1 before, but then I wasn't really using the phone before and tinkering with it. Don't know if it was related to a wrong version of gapps or a dirty rom install or worst case scenario-hardware problems?
I followed the guide here. under TWRP there was an option to Format everything which i haven't tried.
http://www.android.gs/install-paranoid-android-4-2-1-custom-rom-for-google-nexus-4-e960/
gapps 4.2.2
http://donandroid.com/gapps
I also noticed it came with some apps called Android tweaker free and Battery Guru. Could that be cause of it? Compatiblity issues? Should I go back to stock 4.2.1 or try a different rom?

[Q] Issues loading 4.3 rom

Hi Guys,
Just wondering if anyone's knows of a fix for, or even the cause of issues with the SGS4 and Android 4.3 roms.
I have tried 6 different ROMS over the last 3 days and with all of them I get the same result. The ROM flashes fine, the phone reboots in to the ROM and I can set everything up. The ROM will work perfectly for as long as I leave the phone on. For every ROM, as soon as I restart the phone for the first time, it hangs at the SGS4 logo, before the cyanogen spinning circle or the google circles, and does not proceed.
The only way I have found to get it working after it is in this state is to clear the cache, dalvik AND data.
Most of my attempts have been with the CM 10.2 ROM, 10.1 works perfectly but 10.2 has the same issue.
I have tried it with just the ROM, with the ROM and Gapps, with the ROM, Gapps and SuperUser and nothing seems to work.
Just FYI I am using the internation gt-i9505 roms with TWRP (latest version).
Any help would be greatly appreciated!

[Q] [Help] PAC ROM breaking Galaxy S4 (SPH-L720)

Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
D3xus said:
Hello there.
I recently tried to install the most recent version of PAC ROM for my Galaxy S4 (Sprint, SPH-L720, running PAC ROM 23.0 and Android 4.2.2) from their nightly basket builds (I tried to install the November 19th build.) The installation itself goes off without a hitch, as does the GApps installation. However, after installing it (cleaned out the cache and Davlik cache prior to installation, installed GApps after installation), I get multiple error messages. The keyboard process has stopped working, and android.process.acore have stopped working (tells me to blame Tyler.) The device also seems to be laggy in general, and when I try to launch the Phone app, it says it is not installed.
I just want to be able to use 4.3 and PAC ROM's newest features.
If someone can help me resolve this issue or link me to a stable but updated build of PAC ROM, that would be great.
Thank you!
Click to expand...
Click to collapse
You need to do a full wipe from PAC23 to 4.3 (factory reset in recovery)
Figures. :/
What app should I use to backup the contents of my phone to use after the update (messages, apps)

[Q] SYSTEM UI HAS STOPPED, after I updated to the latest nightliy of CM12.1

Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
You don't need to enable debugging, its just that latest cm12.1 build is broken, I just reflashed myself because of that systemui crash, you need to reflash too. You can use version with date 2015-04-16, and then update from the phone using cm integrated updater to version 2015-05-11, because version 2015-05-13 is broken.
Same thing happened to me this morning after I flashed the Nightly of 2015-05-13. I downloaded the Nightly with CyanDelta to reduce the download size and flashed in thorough recovery. After my device booted, I noticed my wallpaper changed and I kept getting "Unfortunately, SystemUI has stopped" error. But it kept showing up every 1-2 seconds making the device unusable. So I just flashed the Nightly of 2015-05-12 which was working and the error stopped showing. Thanks to CyanDelta that keeps a copy of the old Nightly after installing a new one.
I hope that you still have the "stable" Nightly on your device to roll back to the previous Nightly. If you have access to a computer, you might be able to download it directly from CM's website, transfer it thorough USB and flash it with Recovery. That would be the only solution I can come up with beside restoring a NANdroid Backup. But I'm no pro in Android stuff, maybe someone can come up with another solution.
ExcaliburUser said:
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
Click to expand...
Click to collapse
Thanks for the info bro. :good:

Lineage OS 13 bootloop after reboot

EDIT: THIS WAS RESOLVED IN THE NEW 20171231 NIGHTLY, EVERYTHING WORKS PERFECTLY NOW!
So I have this problem with Lineage OS 13 on my N10, so I flash the following packages:
Super SU 2.78
Busy-box
Open Gapps 6.0 nano
Lineage 13 10/14/17 nightly
The first boot is successful, I install some apps, watch some videos, normal tablet stuff. The problem is when I reboot, every time I reboot it ends in a boot loop. The tablet just won't boot up after I reboot it. The first boot works great, but nothing works after-wards.
Doesn't work on mine either, with CM13 20171017 build. I also made comment on the CM14 build thread here on XDA. I couldn't complete the initial setup using the CM14 build. I'm going back to stock.
I have the same problem with 20171021
I was able to reproduce the Error and attatched a logcat.
The bootloop always started while installing the App "immobilienscout24".
Hope someone can examine my logcat. I attached 2 (split) files, because I don't know, what is relevant.
Best regards
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
BerlinOtto said:
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
Click to expand...
Click to collapse
So basically I have to pick my apps wisely or lineage will reboot? **** that noise I'd rather run stock lollipop, lineage on my N10 is awful.
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
I have the same issue of constant boot loops. I tried several LOS nighly build w/o any success.
Funny thing is, after i rolled back to an old CynogenMod backup (v13.0 snapshot from 21.12.2016) it started to boot loop too, after I started updating my apps with Playstore.
So the bug must be very old, and it must be in CM/LOS, not in some specifiy app...
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Marktplaats causes boot loop
In my case, 'marktplaats', a dutch app, caused the boot loop. At some point I decided to upgrade to Lineage. I never had any issues on Cyanogenmod 13.
There seems to be a solution for this Problem in the newest nightly, See
https://jira.lineageos.org/browse/BUGBASH-1052
I've done a test Installation with my two Problem apps and it works fine for me.
I0tacle said:
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
Click to expand...
Click to collapse
All the problems were fixed in the in 20171231 nightly, running it without hitch no, stable and fast MM with CM theme support, finally

Categories

Resources