[Q] Freeze and reboot on initial setup - Samsung Galaxy Nexus

I have a Verizon GNEX, been running an older version of PA for quite a while, went to update to the newest version and on first boot during the initial setup it would freeze and reboot. I have tried everything i can think of, different roms, ODIN, different kernels, but it still will freeze and reboot after a couple taps, TWRP and the bootloader work fine and havent frozen once, I'm doing most of this through the Nexus Toolkit but I just cant get it to work at all.
Ive seen some people have had similar issues and they seems to be hardware related I'm really hoping thats not the case and its just an obscure issue that I cant seem to pin down
Any help would be greatly appreciated.

Most likely is the new CM theme engine bug included in most of the KitKat custom ROMs out there including PA. I found SlimKat to be stable because they're building their own theme engine instead.

Related

[Q] MIUI ROMs - Problem with touchscreen randomly becoming unresponsive and rebooting

Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.
Hopeful bump =)

[Q] 4.1.2 jellybean audio, appstore, and TWRP issues

This is a question regarding Twa_Priv's 4.1.2 10/13 updated ROM.
1,) Does a TRRS headset (headphones with mic) work now? I know that lots of devs were working on getting the mic to work with jellybean, I just don't know if it has gotten around to working on the newly updated ROM
3.) I have had trouble with Amazon appstore not recognizing my KF as a kindle since the last ROM where I clean installed from scratch, so it won't let me install kindle-specific apps. Has anyone had this problem, and does anyone know a way to get around this?
4.) One more issue. I think that this is just a personal problem somehow. I have been having trouble restoring backups. I use Twrp 2.2.2.1 and it seems to create backups fine, it just wont restore them. I haven't tested out if it works with the last 3 builds, because then I have to start from scratch again if it doesn't work, and that takes a lot of time... I had twrp originally then switched to CWM because I thought I had to for an app, then discovered that I REALLY like TWRP better, so reflashed it, and it hasn't worked since then. Any pointers?
thanks

[Q] Random reboots and bootloop even after fullwipe

Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!

Constant random reboots on CM since Cm-10.1-20130316-Nightly-D2Spr

Just like people in this thread: http://forum.cyanogenmod.org/topic/70506-freezes-and-re-boots/
I've looked everywhere. but cannot find any answers.
I've been having trouble with constant reboots ever since any ROM released after cm-10.1-20130316-NIGHTLY-d2spr
Today I saw that there is RC2 available so I decided to try it.
I did my best and got rid of all the 0\0\0\0\ folders (only 1 left it seems), updated Clockworkmod (to the newest I think), then installed the newest RC. (clean install).
Everything was going well until about an hour ago the phone began rebooting again.
Does anyone know what the issue is?
OR if anyone else has a suggestion for a non cm-based rom that is good, let me know.
Did you verify md5sum? Try flashing another kernel right after the ROM flash.

[Q] AOSP keyboard failed to launch?

So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS

Categories

Resources