Database Info

[Q] Having slight problems with CROMI 3.0.4

First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?

furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.

I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?

sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?

furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do

[Q] Is it possible to unroot the Moto G by flashing?

Funny question actually, I recently upgraded from Kitkat to Lollipop by flashing the latest build of the NXE single sim ROM using TWRP. First time I flashed, the setup wizard didn't work so I flashed the cleared the cache and etc and flashed again. That didn't work, so then I flashed the cache, dalvik and system and then the ROM. The setup wizard worked, but for some reason the root access was gone. What did I do wrong? How can this be fixed?

Riqitch said:
Funny question actually, I recently upgraded from Kitkat to Lollipop by flashing the latest build of the NXE single sim ROM using TWRP. First time I flashed, the setup wizard didn't work so I flashed the cleared the cache and etc and flashed again. That didn't work, so then I flashed the cache, dalvik and system and then the ROM. The setup wizard worked, but for some reason the root access was gone. What did I do wrong? How can this be fixed?
Click to expand...
Click to collapse
Flash the SuperSU zip.

rudi_j7 said:
Flash the SuperSU zip.
Click to expand...
Click to collapse
Is there one specific to the Moto G, or is there a generic one I can use?

Riqitch said:
Is there one specific to the Moto G, or is there a generic one I can use?
Click to expand...
Click to collapse
Generic
Sent from my A0001 using XDA Premium 4 mobile app

Riqitch said:
Funny question actually, I recently upgraded from Kitkat to Lollipop by flashing the latest build of the NXE single sim ROM using TWRP. First time I flashed, the setup wizard didn't work so I flashed the cleared the cache and etc and flashed again. That didn't work, so then I flashed the cache, dalvik and system and then the ROM. The setup wizard worked, but for some reason the root access was gone. What did I do wrong? How can this be fixed?
Click to expand...
Click to collapse
Yes, flash CF-Auto-Root search for "falcon" http://autoroot.chainfire.eu/
It has the SuperSU ZIP embedded.

flash supersu v2.39

[Q] Stuck on the bootscreen

So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.

So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon

I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.

There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon

@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo

tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon

I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.

[Q] - No Calls or SMS OxygenOS or CM12

OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.

"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?

abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot

pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again

seems to be sitting stable at the moment, will keep testing. but thanks for the input.

pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.

abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.

Bootloop upon flashing Open Gapps in CyanogenMod 13

Hello!
I could not find any other threads related to this issue, so my apologies if this is a "duplicate" thread
So I found my old Samsung Galaxy Tab 2 10.1 (Model GT-P5113 in Samsung ROM, identified as Galaxy Tab 2 in CyanogenMod) in a cabinet doing nothing, so I thought I would flash CyanogenMod on it and get some use out of it. And so I did; I flashed the nightly build of CM 13 in the "espresso wifi" image. Now, that worked just fine, but when I tried to flash open gapps (open_gapps-arm-6.0-nano-20161217.zip to be exact), I got some sort of boot loop; the device starts and gets into the App Preparer thing (pardon my ignorance) and begins preparing the google apps, and once it does all 16 apps, it starts preparing some other cyanogen mod apps, or at least I believe they are cyanogen mod apps, and then the app preparer just closes, and the boot animation restarts. If I wait long enough, it will once again get to the app preparer and begin flashing 2 apps, I could not see the first one, and the 2nd was the Google app. It would then begin flashing the cyanogen mod apps and then it would close, and the cycle would restart. I flashed Gapps right after flashing cyanogenmod; I did NOT boot into the rom upon installing open gapps. Does anyone know how to resolve this issue? I will provide more information if it is needed. All help is appreciated.

You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Sent from my espresso3g using XDA Labs

Lightracer said:
You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Click to expand...
Click to collapse
Hi, Lightracer, thanks for the reply! I did not boot up the tablet after installing CyanogenMod; however the same result occurs whether I flash it with or without a boot up in between (I needed to reflash CM multiple times)

What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Sent from my espresso3g using XDA Labs

Lightracer said:
What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Click to expand...
Click to collapse
Yes, I am using the right package; arm 6.0 nano with TWRP recovery

What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs

chompy33 said:
Yes, I am using the right package; arm 6.0 nano with TWRP recovery
Click to expand...
Click to collapse
which version of twrp??

smart-t78 said:
which version of twrp??
Click to expand...
Click to collapse
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)

Lightracer said:
What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
I think I wiped it, however, I may have not wiped everything that was required. I will try this and post back.

chompy33 said:
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)
Click to expand...
Click to collapse
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.

smart-t78 said:
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.
Click to expand...
Click to collapse
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!

chompy33 said:
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!
Click to expand...
Click to collapse
You could download the common twrp which works for every samsung galaxy tab 2 model. The newest version is 3.0.2-8 which is found on andi34.github.io under recoveries. This could be useful if you want to flash newer roms.
Sent from my espresso3g using XDA Labs