Database Info

G2x cm10 Paranoid Android Build 8 & 9 Installation

Hello. Before installing the Build 8 & 9 Paranoid Android rom from TonyP (or attempting to install it), I installed the P999 rom from Kashamalaga successfully, although it has no wifi-calling and it also has the battery drain. I wanted to circumvent the battery drain, so I have tried to switch to builds 8 & 9 by wiping the cache & dalvik cache, then flashing the zip with the rom, the gapps and the new baseband zip one after the other. I turn it on and everything is fine except for receiving calls. Am I doing something wrong with the baseband, or anything else? I have tried doing full wipes, but they have not fixed the issue. Thanks in advance.
EDIT: I have been using ClockworkMod Recovery v5.0.2.0 and I have been doing the following:
wipe cache->yes->advanced->wipe dalvik->yes->install zip from sd card->choose zip from sd card (3 times)->pa jb rom buildx->newbaseband.zip->gapps.zip->reboot
EDIT2: It works now. Did a full wipe and I believe I did newbaseband->build9->gapps. Someone correct me if I should do it otherwise but I'm currently testing it to make sure everything else is working (calls fixed).
EDIT3: The battery is still a bit wonky even after doing a battery stats wipe, but it has extended battery life for the most part

[Q] P5100: CM10.1.2 + Kernel Dhollmen: trying encryption leads to bootloop

hello,
I've installed Dhollmen kernel 20130722 on top of a Cyanogenmod 10.1.2.
The recovery is PhilZ Touch build 5.05.0 p5100 (CWM base 6.0.3.2).
All works fine, but my troubles begin when I try to password-encrypt the tablet (Settings -> Security -> Encrypt tablet).
The encryption process requires a restart, but then the Cyanogenmod logo appears and begins to roll and nothing else happens!
After two hours the logo still rolls.... at this point I did a reset and newly performed a clean install of CM 10.1.2 to get back a working tablet.
Note: if I install only CM 10.1.2 (that is, without changing his official kernel), the Encryption process completes successfully, so I wonder if the problems are related to the Dhollmen kernel.
However, since I truly love this kernel, I would like to use it, but I cannot renounce to encryption (for security reasons).
Any idea?

loboz said:
hello,
I've installed Dhollmen kernel 20130722 on top of a Cyanogenmod 10.1.2.
The recovery is PhilZ Touch build 5.05.0 p5100 (CWM base 6.0.3.2).
All works fine, but my troubles begin when I try to password-encrypt the tablet (Settings -> Security -> Encrypt tablet).
The encryption process requires a restart, but then the Cyanogenmod logo appears and begins to roll and nothing else happens!
After two hours the logo still rolls.... at this point I did a reset and newly performed a clean install of CM 10.1.2 to get back a working tablet.
Note: if I install only CM 10.1.2 (that is, without changing his official kernel), the Encryption process completes successfully, so I wonder if the problems are related to the Dhollmen kernel.
However, since I truly love this kernel, I would like to use it, but I cannot renounce to encryption (for security reasons).
Any idea?
Click to expand...
Click to collapse
Ask the dev :cyclops::cyclops::cyclops:

I apologize, the problem doesn’t concern Dhollmen kernel, I’ve tried to install another kernel (Blackhawk) over CM and the issue was always the same: bootloop when trying to encrypt.
It’s clear that I’m doing something wrong, but I don’t know what!
In doubt, I’ve tried to start from a “clean” state; from CWM 6.0.2.7:
1. Format “/data/” and “/data/media/”
2. Format “/cache/”
3. Format “/preload/”
4. Format “/system/”
5. Flashed CM 10.1.2 (from external sd)
6. Flashed google apps (from external sd)
7. Flashed kernel (from external sd)
When I restart the tablet all seems to work fine, but when I try to encrypt… bootloop!
I’ve tried to connect the tablet to the PC to verify if logcat can help, but the device wasn’t detected at all...
At this point I’ve tried some variants (I’m desperate, I know ):
- I did a prudential reboot into CM after flashing it, and before flashing the new kernel.
- I’ve flashed CM, encrypted the tablet (encryption is successful with original CM kernel), and only after encryption I’ve tried to flash the new kernel.
- I’ve tried with: CM 10.1, 10.1.2 and 10.1.3rc2
… but the result is always… bootloop.
Any idea? What am I missing?
EDIT: I've installed a nightly version of CM 10.2, then Dhollmen custom kernel.
Encryption process ended successfully.
As suggested by tuxafgmur, there was some incompatibilities between CM 10.1 and his kernel, that can be solved only upgrading to CM 10.2.

[Q] 4.1 ROM Recommendations

Hi all. Like the title says, I need a 4.1 ROM. 4.2 and .3 do not work with WiiMote app. I use this function a lot. I'm new to TF so I don't know my way around. I came from the Iconia which had 4.1. Can anyone recommend a stable decent performing ROM with 4.1?
Thanks

TeamEOS 3 #81 was a great 4.1 ROM
http://forum.xda-developers.com/showthread.php?t=1782410
ROM
http://goo-inside.me/devs/teameos/roms/eos3/nightlies/tf101//EOS-tf101-20121027-81.zip
Recommended Kernel (Really improves performance)
KatKernel_70_Lidpatch.zip
Gapps (I forget which version we used to use, but I guess these should work)
http://goo-inside.me/gapps//gapps-jb-20121212-signed.zip
Make sure you are running TWRP Recovery prior to flashing the ROM
http://forum.xda-developers.com/showthread.php?t=1818452
Flash TWRP
Boot into TWRP Recovery
Wipe SYSTEM / CACHE / DALVIK CACHE (Optionally Wipe DATA / FACTORY RESET etc etc for 100% clean install)
Flash ROM
Flash Kernel
Flash Gapps
Wipe CACHE & DALVIK CACHE
Reboot

Thanks Detection. I'll check it out. It makes sense since I've been using KatKiss 4.2 so far and really like it. I think I read that he was part of EOS originally. Should be good.

Yep that's true, TeamEOS became what is now KatKiss and was definitely one of, if not the most popular ROMs for the TF back then

[Q] boot issue with cyanogenmod 11

Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated

Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.

Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM

Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.

Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know

Paranoids works fine, seems like a CM problem .-.

Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod

Touch screen not responding/working

Hello guys
After running cm13 without nog problemen for over a month I got an update today and installed it as usual (using cwm). However I also run ElementalX custom kernel. When you install a new version of Cyanogenmod it flashes it's own kernel over the custom kernel. Normally I would flash the cm update, wait for it to finish, reboot into recovery again and then flash ElementalX. However today I tried to flash ElementalX directly after installing the cm update. It reboots like normally and all the hardware works but my screen is not responding. I have tried installing a backup, wipe user data , dalvik cache etc but nothing is working. Can one of you help me?
Nexus 5
Cyanogenmod 13
ElementalX
ClockWorkMod