Database Users

[Q][HELP]Compiled CM10.2 for official unsupported device, but cannot boot up.

I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!

lackyking said:
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
Click to expand...
Click to collapse
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.

simms22 said:
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
Click to expand...
Click to collapse
I tried, but also stopped on the first screen of manufacture logo.

lackyking said:
I tried, but also stopped on the first screen of manufacture logo.
Click to expand...
Click to collapse
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?

simms22 said:
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
Click to expand...
Click to collapse
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.

lackyking said:
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
Click to expand...
Click to collapse
youre not the only one that the latest cm code isnt booting up on.. http://forum.xda-developers.com/showthread.php?t=2435980

[Q] Galaxy S5 G900F + TWRP 2.8.3.0 + CM11 = wrong date & time

Hi, I have some weird behavior with date and time in CM11 and CM12 - through settings i try network time and then manually but after reboot it reverts back to 1st January 2014 - Very Strange and anoying!!!
Then if i connect wifi or data on phone, the time goes correct!
Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 or CM12 after reboot and for TWRP What can i do?
What i have tried:
Factory reset
Tried CM11 and CM12
Other versions of TWRP
Tried ktoonsez kernel.
Im out of options, what i need to do? Im very very upset and tired of this problem.

Please help guys

That is a cyanogen open issue, find it and try a solution that's there about setting time one hour ahead. It worked for me

P4k1t0 said:
Please help guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52681863&postcount=3284
This is the solution that worked for me

venereo said:
http://forum.xda-developers.com/showpost.php?p=52681863&postcount=3284
This is the solution that worked for me
Click to expand...
Click to collapse
I have tried that like 5 times now, and nothing
Also tried this:
http://forum.xda-developers.com/showpost.php?p=52742566&postcount=5
And nothing also.
The problem is i have allready make a factory reset, and time on TWRP is also wrong!!

Did you try flashing stock back?

venereo said:
Did you try flashing stock back?
Click to expand...
Click to collapse
No, i have tried Factory Reset by TWRP: Wipe data, cache and dalvik cache.

Any reason not to try it?

venereo said:
Any reason not to try it?
Click to expand...
Click to collapse
I will have a lot of work, for just a 'stupid' bug

Flashing through Odin it's a lot of work? You had most of the work already
---------- Post added at 05:43 PM ---------- Previous post was at 05:15 PM ----------
P4k1t0 said:
I will have a lot of work, for just a 'stupid' bug
Click to expand...
Click to collapse
first set correct time then delete time_daemon from system/bin, reboot!
Try this

venereo said:
Flashing through Odin it's a lot of work? You had most of the work already
---------- Post added at 05:43 PM ---------- Previous post was at 05:15 PM ----------
first set correct time then delete time_daemon from system/bin, reboot!
Try this
Click to expand...
Click to collapse
Thanks for your reply, yes also tried that, nothing
Also tried changing TWRP to CWM like @loudambiance said there: http://www.reddit.com/r/cyanogenmod/comments/2r0bwm/galaxy_s5_g900f_twrp_2830_cm11_wrong_date_time/
And nothing.
Also restored my phone to one backup i have from 2014-07-03 - OmegaV11, and the problem was solved, reboot sucesfull and time was ok, but when i change to CM11 or CM12, the problem happens again!

P4k1t0 said:
Thanks for your reply, yes also tried that, nothing
Also tried changing TWRP to CWM like @loudambiance said there: http://www.reddit.com/r/cyanogenmod/comments/2r0bwm/galaxy_s5_g900f_twrp_2830_cm11_wrong_date_time/
And nothing.
Also restored my phone to one backup i have from 2014-07-03 - OmegaV11, and the problem was solved, reboot sucesfull and time was ok, but when i change to CM11 or CM12, the problem happens again!
Click to expand...
Click to collapse
Flashing with Odin will get stock recovery back, maybe you could restart from there

venereo said:
Flashing with Odin will get stock recovery back, maybe you could restart from there
Click to expand...
Click to collapse
Yes, but then i have to re-root again, install an recovery so i can install CM right? And what if the problem get back again?

P4k1t0 said:
Yes, but then i have to re-root again, install an recovery so i can install CM right? And what if the problem get back again?
Click to expand...
Click to collapse
What do you want me to say? It is a CM problem, you either install CM and live with it's problems (they are well known) or you keep tw from sammy

venereo said:
What do you want me to say? It is a CM problem, you either install CM and live with it's problems (they are well known) or you keep tw from sammy
Click to expand...
Click to collapse
Yes i know, lets see if anyone have a new solution for this.

P4k1t0 said:
Yes i know, lets see if anyone have a new solution for this.
Click to expand...
Click to collapse
I understand, but as you saw already it keeps unsolved in cm forums. That's a bad sign

If you do experience this issue, make sure to REPORT IT on the cyanogenmod bugtracker or at least vote for the issue so that someone will eventually look at it. https://jira.cyanogenmod.org/browse/CYAN-4915

Moto X pure keeps on restarting

My moto x pure keeps on rebooting and I think it is bootloader related as I accidentally pressed on the restart bootloader option in fastboot and my issues began since. I tried flashing 3 different roms since that and it still does the same thing, open for a few seconds then go to the ' Warning bootloader unlocked screen' boots into the rom and repeats. If anyone can provide any help i will really appreciate it since I can't find any solution.

Philo0o said:
My moto x pure keeps on rebooting and I think it is bootloader related as I accidentally pressed on the restart bootloader option in fastboot and my issues began since. I tried flashing 3 different roms since that and it still does the same thing, open for a few seconds then go to the ' Warning bootloader unlocked screen' boots into the rom and repeats. If anyone can provide any help i will really appreciate it since I can't find any solution.
Click to expand...
Click to collapse
Try flashing stock firmware.

yk1999 said:
Try flashing stock firmware.
Click to expand...
Click to collapse
is there any other solution?? If not how do I flash stock rom?

Philo0o said:
is there any other solution?? If not how do I flash stock rom?
Click to expand...
Click to collapse
I can't understand what the problem is but flashing stock firmware solves many problem.
Is there something wrong with bootloader flashing stock firmware with bootloader can solve it.
Is your phone model xt1575 . If so then read this
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110

What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.

acejavelin said:
What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.
Click to expand...
Click to collapse
Hey ace, is f2fs actually prone to crashes? And are there performance improvements? I run handbag 2.3.3 and their thread says there should be no corrupting of data or issues with f2fs, but I wondered if I would see improvements with it?

Spencervb256 said:
Hey ace, is f2fs actually prone to crashes? And are there performance improvements? I run handbag 2.3.3 and their thread says there should be no corrupting of data or issues with f2fs, but I wondered if I would see improvements with it?
Click to expand...
Click to collapse
No, it's fine... just some ROM's, or more accurately some kernels, don't support it... such as stock Marshmallow.
In theory it's better for flash based devices, but in real world testing with Android devices it makes little difference.

acejavelin said:
No, it's fine... just some ROM's, or more accurately some kernels, don't support it... such as stock Marshmallow.
In theory it's better for flash based devices, but in real world testing with Android devices it makes little difference.
Click to expand...
Click to collapse
Okay thanks so much! I know there were issues with previous issues of handbag but those were fixed so it should be fine, but I guess there's no reason to change, thanks!

acejavelin said:
What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.
Click to expand...
Click to collapse
I see, how do I change the data partition? All the tutorials I see are ext4 to f2fs conversion and not vice versa. Thank you

Philo0o said:
I see, how do I change the data partition? All the tutorials I see are ext4 to f2fs conversion and not vice versa. Thank you
Click to expand...
Click to collapse
Same thing. Exact same thing. TWRP -> wipe -> advanced wipe -> change data format and then change to ext4

Spencervb256 said:
Same thing. Exact same thing. TWRP -> wipe -> advanced wipe -> change data format and then change to ext4
Click to expand...
Click to collapse
I tried changing to both and now it doesn't even boot into the system, just stuck on the 'warning bootloader unlocked screen'

Philo0o said:
I tried changing to both and now it doesn't even boot into the system, just stuck on the 'warning bootloader unlocked screen'
Click to expand...
Click to collapse
You have to reflash the stock image after changing the partition type.

acejavelin said:
You have to reflash the stock image after changing the partition type.
Click to expand...
Click to collapse
Thank you I flashed the stock recovery and it works okay now. One last thing, does this mean I can't flash custom roms anymore?

I had this problem with a few customer ROMs I tried. Using Resurrection Remix 5.8.4 now and have not had that problem.
https://forum.xda-developers.com/mo...unofficial-resurrection-remix-v5-8-3-t3637204

My phone keeps resetting even when trying to get into recovery. When i'm in system it's like somebody is randomly pushing power button. Is there something i can do with it? I tried flashing stock ROM and it's still the same.

I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.

lmulli said:
I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.
Click to expand...
Click to collapse
I think you didn't flash any of this:
RRemix 24.04 + handbag or simple kernel,
RRemix 14.08 + any kernel,
Dirty Unicorns any build.

dzidexx said:
I think you didn't flash any of this:
RRemix 24.04 + handbag or simple kernel,
RRemix 14.08 + any kernel,
Dirty Unicorns any build.
Click to expand...
Click to collapse
I've tried them, and as stated above, none are as stable/smooth as stock. Fact. You can quote every custom rom and kernel combo you like, it doesn't change that fact.

lmulli said:
I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.
Click to expand...
Click to collapse
What? Link us plz

Why camera don't works on andriod 7.1 ?

Hi ,everyone . I tryed many android 7.1 roms , like aicp , omni , lineage , mokee , everything is ok . But all those roms , the camera didn't works , said can't connect to the camera . I tryed other camera apps , they also didn't work . When I flash back to android 6.0 , its ok . Anyone know why ? And how to solve ?

What u edition ?
X720 or x727 or 722 or x651 ?

ajegile said:
What u edition ?
X720 or x727 or 722 or x651 ?
Click to expand...
Click to collapse
it is x720.

This is the first time I've heard, you're the first

Perhaps a good old "format" to system and data partitions can help! Then retry...

orsonbear said:
Perhaps a good old "format" to system and data partitions can help! Then retry...
Click to expand...
Click to collapse
I have formated data , system , cache , dalvik , and flash the rom . It also happen .

Try formatting the partitions this way:
From TWRP recovery, Wipe, Advanced wipe, choose Data, Repair and change file system, Repair file system, then swipe to right.
The same with System partition then retry flashing LOS 14 and latest Open Gapps pico or nano for Android 7.1 ARM64. Finger crossed!
There are other things you can try to solve the problem, but perhaps the best thing to do is bring the system back to the original factory rom and condition and start from there. Cheers!

orsonbear said:
Try formatting the partitions this way:
From TWRP recovery, Wipe, Advanced wipe, choose Data, Repair and change file system, Repair file system, then swipe to right.
The same with System partition then retry flashing LOS 14 and latest Open Gapps pico or nano for Android 7.1 ARM64. Finger crossed!
There are other things you can try to solve the problem, but perhaps the best thing to do is bring the system back to the original factory rom and condition and start from there. Cheers!
Click to expand...
Click to collapse
I will try it . But I think that may not work. Because I have changed the /data into f2fs , flash the rom , it doesn't work. And , I using the original factory rom , 23s , it works fine , so I might try the LOS 14 in few weeks , or when it has important update.

If everyone has the same problem , please post there. I don't think it's single case. Because I saw such cases in Chinese BBS. If there is any suggestion, I will be very grateful.

orsonbear said:
Try formatting the partitions this way:
From TWRP recovery, Wipe, Advanced wipe, choose Data, Repair and change file system, Repair file system, then swipe to right.
The same with System partition then retry flashing LOS 14 and latest Open Gapps pico or nano for Android 7.1 ARM64. Finger crossed!
There are other things you can try to solve the problem, but perhaps the best thing to do is bring the system back to the original factory rom and condition and start from there. Cheers!
Click to expand...
Click to collapse
Well , I flash back stock eui 26s , then flash onmi , but the camera still don't work . I think this is a hardware issue .

It is possible that Leeco has mounted another camera.
Look for some utility that tells you what type of camera hardware you have, and check if it is the same as the others.
Greetings.

my x720 camera also can't connected. and dont know howto do.

Same here my camera only work on stock otherwise it says can't connect camera. Phone model is LEX720.

Hello
Have you solved it? I have the same problem
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
danishashraf047 said:
Same here my camera only work on stock otherwise it says can't connect camera. Phone model is LEX720.
Click to expand...
Click to collapse
Hello
Have u solved the problem?
I have the same problem

Yukimidas said:
Hello
Have you solved it? I have the same problem
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
Hello
Have u solved the problem?
I have the same problem
Click to expand...
Click to collapse
No bro, I'm also suffering from this issue.

aicp15 also cant use camera.

I have the same problem. Anyone has solution?

ozanselte said:
I have the same problem. Anyone has solution?
Click to expand...
Click to collapse
Yes, install Paranoid 7.3.1 - There are no issues with the camera or anything else.
I have the X727 and It is an absolutely perfect Rom with 7.1.2 Android.

tsongming said:
Yes, install Paranoid 7.3.1 - There are no issues with the camera or anything else.
I have the X727 and It is an absolutely perfect Rom with 7.1.2 Android.
Click to expand...
Click to collapse
Did you have this problem before?

ozanselte said:
Did you have this problem before?
Click to expand...
Click to collapse
I have not had an issue with the camera. But I noticed improvements to the camera after upgrading from stock 5.8.18s to 5.8.21s. In fact there were many dramatic improvements.
Next, before I installed Paranoid I did a full system wipe....I'm wondering if maybe some people are experiencing issues related to a dirty install?
I have used Paranoid 7.3.1, for over a week and I an very satisfied with it. I don't think the battery is as efficient it was on as stock. But, resolved that by installing Greenify.
Also, the quick charge is significantly faster.. So fast that i don't think the quick charge function worked at all on stock.

Can someone help me pls(?

First of all, i apologise for my english, second of all, the problem indeed: Why i can't install DotOs, CosmicOS, or CardinalOs? (Whenever i tried to flash ROM first and TWRP to proceed to reboot on recovery), my screen just goes crazy... I read on a couple of comments, that some roms have bugs on screen touch drivers, and i already try to install a custom kernel but didn't work... I tried RR, PE, Bootlogers, LineageOs and they work well... Pls HELP XDA-KUN ??

I'm not a developer, so I can't tell you why. But If I was you, I'd try reflashing your TWRP. Also, I recommend installing AOSPExtended out of all these ROMs.

SmallTarzan said:
I'm not a developer, so I can't tell you why. But If I was you, I'd try reflashing your TWRP. Also, I recommend installing AOSPExtended out of all these ROMs.
Click to expand...
Click to collapse
I see myself as a tester, so i like to try every ROM that is out at the moment... I try reflashing TWRP and is the same thing... I also tried wiping internal storage and so, but nothing happends...

Fors4kenArg said:
I see myself as a tester, so i like to try every ROM that is out at the moment... I try reflashing TWRP and is the same thing... I also tried wiping internal storage and so, but nothing happends...
Click to expand...
Click to collapse
@sooti can u help me pls?

Fors4kenArg said:
I see myself as a tester, so i like to try every ROM that is out at the moment... I try reflashing TWRP and is the same thing... I also tried wiping internal storage and so, but nothing happends...
Click to expand...
Click to collapse
You may want to try flashing a different recovery: https://forum.xda-developers.com/mi-a1/development/recovery-red-wolf-recovery-project-t3753157