• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[rom][alpha]AOKP 41

before installing can you open up the rom's build.prop and change this line:
persist.adb.notify=0
To this:
persist.adb.notify=1
(it is on line 133 if you use notepad++)
Then wipe data, then try to pull a log.
Thanks in advance
 
what operating system are you on? If someone with linux can try to pull a log that would probably work. If nothing shows up try running it as lusb and it should show the device.
 
That's probably why... I am getting my new lucid tomorrow so I can try to pull a log on my linux partition. I have no idea why but linux is better for everything that has to do with android.
 
That's probably why... I am getting my new lucid tomorrow so I can try to pull a log on my linux partition. I have no idea why but linux is better for everything that has to do with android.

Maybe because Android is built off Linux :P (sorta)
 
And because Linux is friggin great. I can pull logs from terminal for anything you need. Also. Has anyone tried flashing from stock GB and pulling a log? If not, I can try.

I got it to flash by the help of stcarlso. I need a log of when it has been booting for a few minutes (Bootloop) If you can pull a log after it has been booting for a couple of minutes that would be awesome.
 
so any progress on this? its pretty exciting seeing an active development of a rom for the lucid. its a great little phone but cm10's development seems to have stopped.
 
trust me, Dev hasn't stopped for cm10. I am going to take another shot at this when the new cm10 is released. (or even cm10.1!)
 
That's great to hear. I like cm10 lots but it's definitely not perfect yet. And I'd like to switch it up and use yours hopefully. And news on cm10s development?
 
I have installer A3 from stock GB and it flash but get stock on initiate swagger animation, can someone help me with this?
 
That's great to hear. I like cm10 lots but it's definitely not perfect yet. And I'd like to switch it up and use yours hopefully. And news on cm10s development?

Well cm10 is almost perfect besides sod and reboots (which don't even happen to me :) ) I think either b3 or cm10.1 are coming out soon. Once they do I will attempt at making this rom work! If you know how, after this rom bootloops for a couple of minutes can you pull a logcat through adb? Especially if you have something running linux.
 
Yeah I get reboots fairly regularly. My other things is it'll auto over clock to 1512ghz killing my battery life. And it'll a few other small bugs. No sadly no Linux but If I can help other ways I'll try my Hardest
 
A2 didn't flash, I checked the updater script and nothing. I couldn't fix the status 7 error.
 
No, but it is one step closer to working. while it does flash, it does't boot. Its probably another stupid problem. Can you pull an adb logcat after this has bootlooped for a couple of minutes, if you can. If you have linux it will be much easier.
Do NOT flash unless you are planning to pull a log because this will not boot,
 
No, but it is one step closer to working. while it does flash, it does't boot. Its probably another stupid problem. Can you pull an adb logcat after this has bootlooped for a couple of minutes, if you can. If you have linux it will be much easier.
Do NOT flash unless you are planning to pull a log because this will not boot,

I'll do this in a few days, I need my ADB back. I restored my computer and lost it, but I'll try pulling a log when I do.
 
No, but it is one step closer to working. while it does flash, it does't boot. Its probably another stupid problem. Can you pull an adb logcat after this has bootlooped for a couple of minutes, if you can. If you have linux it will be much easier.
Do NOT flash unless you are planning to pull a log because this will not boot,

I have two lucida that have no service for testing. I can pull logs on my strictly Linux computer. Drivers are so annoying.
 
Back
Top Bottom