Database Users

[Q] Help! Quarks CM10 does not boot

I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?

atlcr said:
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
Click to expand...
Click to collapse
Nevermind...apparently pressing vol. down when the LED flashes blue gets me to a boot menu. Pheww!

Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.

Please ask all questions in Q&A. Thread moved there.

atlcr said:
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Click to expand...
Click to collapse
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.

3ze said:
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
Click to expand...
Click to collapse
I don't think he has to flash the sbf, just flash gapps n wipe data n cache. also try dalvik cache
Sent from my MB526 using xda premium

You could simply install a new .zip from recovery. You could use the same CM10 11/28 or any other rom. This shoud work out for you.
I experienced the same with my Defy today and I installed a new CM 10 09/05 by Epsylon and it worked like a charm.

Thank you for the replies!
I had to flash it a hundred times to get it to work (I kept getting write access errors for cache folder). What ended up working was to wipe everything and install the 9/24 build. From there, I rebooted and installed (without wiping) the latest build along with the correct gapps. It works fantastically now! My phone is soo much more responsive and I'm loving CM10.
3ze had it right. I was using the latest gapps (12/2) instead of the "minimal" version in the quarx dir.
I haven't noticed a battery drain as has been widely reported here. In fact, it seems to be less of a drain now though that is likely due to the fact that I wiped everything and only installed apps I needed this time around. Tons of unnecessary apps could explain why my battery life was less before.
I have noticed a slight difference in reception now though. Places that used to be fine for connecting to the network (Tmobile) have now become less strong and frequently dropping out. I wonder if the signal strength could have been messed with?

[Q] Systemui keeps crashing on custom roms

Need some expert assistance. The problem is my phone keeps crashing with systemui errors when using custom roms. It always happens after a reboot and usually within 1-3 days, depends on WHEN I reboot the phone. Let me give you a little backstory.
A little over a month ago, I was running AICP on my phone, but decided to try SimpleAOSP and Hells doctor.. So I created a backup in TWRP, then flashed SimpleAOSP and HD. The next day day I started getting the errors. At the time, I thought it was the kernel or a Titanium Backup glitch.
So I wiped and reflashed SimpleAOSP without HD and without restoring from TB. But the next day, systemui failed to start. I thought it might be a rom issue so I restored AICP from my TWRP backup. And I couldn't believe it when the same systemui errors happened. So I restored the backup again. Again it was okay for a few days, then error.
After that I copied everything from my phone to the PC and wiped internal storage. Then installed the same rom version from AICP that I had been using for weeks prior to all this. Same error after a few days.
So next I tried wiping internal storage again and flashing stock 4.4.4. I used that for over a week with no system errors. So I did a TWRP backup of Google stock rom, Then installed AICP again but this time without modifying any systemui type settings, I left the rom as stock as it could come. Didn't even restore apps or anything. I then the rebooted the phone a couple of times to test and the error came back. This was the same day I installed it.
So I restored the stock backup and have been running fine all week. I want to get back on a custom rom though. Any suggestions?

Am I getting no replies because I'm missing something really obvious?
Or can no one think of anything that I haven't already tried?
By the way, right after posting the OP I installed the L preview and it's been working fine so far. I figured if I had to run stock android it may as well be the latest thing.
Sent from my Nexus 4 using Tapatalk

I don't have any answer to your question but I was wondering if this happens without installing a custom kernel on CM11 and AOSP custom ROMs.

Thanks for replying.
When I tried SimpleAOSP, it was with and then without an additional kernel. I saw no difference as far as the error is concerned. I have not tried a CM11 based ROM since this all started.
Maybe I should try a custom rom that doesn't have heavy modifications like AICP has.
Sent from my Nexus 4 using Tapatalk

Are you flashing a Gapps package? A couple weeks ago when I was trying different ROMs I was getting system crashes after flashing PA Gapps and they updated. I never narrowed it down, but after uninstalling a bunch of them (News/Weather, Talkback, Keep, Newsstand, some others) so they wouldn't update, I stopped getting system crashes.

Idk why I have the feeling your theme/icon pack has something to do with it. I run pa and whenever I try to use click ui icon pack it happens to me but if I just run veu I don't have a problem. Try not using themes for a bit to see what happens

Sorry, I missed your responses, I had kinda given up on the whole thing. Android L is running good for an unfinished product.
Getting back to the original issue, no theme or icon pack was installed.
Yes, I was using PA gapps mini from 9-23. Maybe that was it.
But that would be weird because I don't remember my first ROM running PA gapps, not 100% sure... that was a month ago.
I'll try to install without any gapps package and report back. Thanks.
Sent from my Nexus 4 using Tapatalk

from my past history, I'm facing issues when I did 3 things :
1. if I just dirty flash or factory reset only before flashing new rom.
2. Did restore backup from TB (which from your explanation above, you don't have any problem TB)
Nowdays I always use wipe dalvik, system, data, cache. Because someone once told me if you changing roms, if not it's possible that the system setting from old rom will crash with the new ones. and for the wipe system part (some roms included that command in their roms zip file and some didn't).

Resurrection Remix ROM 6.8 Build running Kernel 6.2 - Bootloop Issue Zenfone 5

Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!

Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?

tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.

Just format again and re flash rom with xposed it fixed my bootloop.

The solution is,
Go back to stock rom. ???

Can anyone tell me how to back stock ROM from resurrection remix???

yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.

I m now on Stock Rom without any problems no screen freeze no bootloops ...

[i9505] Cannot enter Recovery after Format Data

My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.

vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.

I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.

vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later

If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.

OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.

vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.

vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/

GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?

vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.

vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.

I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!

can't update past LineageOS 14.1 20171013

Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.

Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.

Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.

fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha

If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.

I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).

Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.