yashsingh1/xdaforums huggingface dataset:
[RAZR HD Android Development] madmonkey57:
I don't have a twitter account (and I don't want one, my social skills are limited...:eek:).

I'd appreciate if another xt925 owner out there could kindly inform dh about the "black screen" that we are experiencing with TWRP2841-xt925.

FYI, I was able to flash 1/18 with twrp2830-unified AFTER I manually removed the offending "ASSERT".
[RAZR HD Android Development] cleiton.a:
This happen with my xt925 have a long time.... idk why... But to resolve you just need reboot the recovery... Sometimes I need reboot the recovery several times.. But this alway work for me... Have I installed the DHacker TWRP 2.8.4.1xt925 with success and this is fully working...

Btw 20150118 CM12 Official for XT925 isn't working... Bootloop for me like for everyone...
[RAZR HD Android Development] madmonkey57:
I know that I can get TWRP to work once every few boots, but this isn't exactly "fully working". There is something wrong.
[RAZR HD Android Development] niksy+:
There's something about this black screen bug...

On my XT925 (it's a Canadian XT925) I got a black screen with philz_touch_6.58.7 every time and then CWM 6.0.4.9 worked fine and then I replaced it with TWRP (which is my favourite, tbh) 2.8.3.0 and it also worked fine. Every time.

Then, a few days ago we bought an XT926 for my dad and the situation was rather different on it. TWRP 2.8.3.0 booted with a black screen each time, and when I flashed PhilZ 6.58.7 it works fine but with a black screen on every 2nd or 3rd boot to recovery.

There's definitely an issue behind all this, but I've no idea what it is. Nobody had these problems on JBBL, afaik, so at least that narrows it down a bit.
[RAZR HD Android Development] madmonkey57:
Agree. My own experience is:

- TWRP 2.8.1.0: OK

- TWRP 2.8.2.0: Black screen

- TWRP 2.8.3.0: OK

- TWRP 2.8.4.0 (xt926, maybe I shoud've refrained from flashing...): Black screen

- TWRP 2.8.4.1 (xt925): Black screen

I tried to disable "Screen timout" in settings but it didn't make it any better...
[RAZR HD Android Development] cleiton.a:
Yep... This problem start after KKBL... Maybe something different in KKBL...
[RAZR HD Android Development] Zeljko1234:
I'm not big fan of social networks but I have twitter account to follow few guys. Just twitter dhacker about xt925 problem.

There are two assert lines. Did you remove both?
[RAZR HD Android Development] lcc014:
Thanks. if black screen issue is fixed, then I would like to try TWRP recovery.
[RAZR HD Android Development] madmonkey57:
No, only the first line of the script.
[RAZR HD Android Development] CWGSM3VO:
The black screen on recovery for KKBL is well known. In PhilZ, you can use gestures to wake the device (followed by a volume key) when it happens. I've tried all the stuff I've seen like disabling screen dim, etc. None of it works.

I think I'm going to start building my own recovery. The CM one is OK but lacks the backup/restore which I use a lot.
[RAZR HD Android Development] madmonkey57:
I just mailed dh.
[RAZR HD Android Development] CWGSM3VO:
Nightlies should start happening again, this commit http://review.cyanogenmod.org/#/c/85896/

Definitely works for me, was able to revert the workaround commit I mentioned in the comments and build + flash this morning.

Kudos to DH, it was a nice catch.
[RAZR HD Android Development] ermito:
Strange. I never had this black screen bug on recovery. I've been using TWRP a long time ago, just changed to cm recovery to install latest nightlies and returned to TWRP 2.8.4.1.
[RAZR HD Android Development] Zeljko1234:
Removed the first line, flashed with latest twrp and got loop again :eek: Maybe because of dirty flash?
[RAZR HD Android Development] madmonkey57:
I meant on C's 1/18, not on lastest nightly.
[RAZR HD Android Development] gappledroid:
:confused: There arent any 20150119 CM12 Official for xt9xx devices at the time of writing this comment. You flashed another...
[RAZR HD Android Development] djvita:
So many cahnges good job guys

things have moved quickly!

decided to RSD from JB, since i found out unfortunately that gps must be on in kk (like jb) to have it working on lollipop. downloaded latest rom from bliss, latest twrp, and gapss. wish me luck!
[RAZR HD Android Development] cleiton.a:
Sorry... Typo... 20150118...
[RAZR HD Android Development] Thibault1171:
Hi guys, sorry to post it here.

Since yesterday, I can't use my phone (I took my old one for today).

I've flash C's recovery based on CM recovery, then tried to flash the 1/18 build, ended on a bootloop as everyone.

But I can't flash any other builds since this recovery is saying the zips aren't for vanquish_u, or random error with every zips I've tried so far.

So I said to myself: try to install another recovery. I've installed adb, and I try this way to flash a recovery:

adb wait-for-device

adb reboot bootloader

fastboot flash recovery.img

First time wait-for-device installed drivers on my computer, then nothing else in about 10 min, so I quit cmd and reboot phone. But now wait-for-device didn't do anything, and if I directly try reboot bootloader, it says that device not found.

What can I do to have a working phone again.

Thanks !
[RAZR HD Android Development] CWGSM3VO:
Assuming you flashed my CM recovery I posted up, flash the 1/18 build I posted (you weren't clear if this is what you did). This all requires that your phone has been upgraded to Kitkat, otherwise, it'll never work.

Keep in mind that nightlies should be returning to normal now that the boot issue has been resolved.
[RAZR HD Android Development] Zeljko1234:
Which OS? For windows you have to install drivers. Easiest way is to download minimal adb and fastboot, install, reboot your phone to bootloader, go to device manager, right click to unknown device (should be your phone), update driver, find google or android (don't remember exactly), install drivers. Now you should be able to fastboot flash latest_twrp.img (I've posted links here recently)... You know rest.
[RAZR HD Android Development] elborak:
It's far easier to enter the bootloader with the VolUp+VolDown+Power method than using adb.

Then just fastboot your recovery as usual.
[RAZR HD Android Development] Thibault1171:
Yes, I'm on KKBL, and using CM12 for half a month. No, I downloaded the 1/18 official build and ended with a bootloop. Can you please give me a link of one of your fonctionnal build please?

When I try to flash your 1/17 build, I ended up with this error:

Install failed
E:Cannot load volume /misc!
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
E:cannot load volume /misc!

EDIT: I've only used fastboot as you suggested and the recovery is here. Thanks. Now trying to flash
[RAZR HD Android Development] CWGSM3VO:
This error looks like an incomplete/damanged ZIP file.

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

adb reboot bootloader

:D
[RAZR HD Android Development] Zeljko1234:
Just dirty flashed C's build and finally can customize quick settings :)

Anyone knows nice dark theme?
[RAZR HD Android Development] Thibault1171:
Finally booted on 1/17

Sorry for all of this, and thank you all for your help !
[RAZR HD Android Development] elborak:
Sure, if your system is already setup for adb. But when I see people struggling to get the right drivers installed just so they can type "adb reboot bootloader" it makes me scratch my head.
[RAZR HD Android Development] CWGSM3VO:
Fair enough. I've always believed that having a working adb is a requirement for running custom ROMs. There's *plenty* of information out there on how to set it up properly (and plenty of folks giving help on how to do so, such as Z did).

Irks me when people can't produce captures because they can't be bothered to set up an environment conducive to doing so. I don't mean those struggling to do so (at least they're trying).

Although I may be unrealistic in my opinion, after all, it's all free and no support is guaranteed so why bother making it easier? :)

just my two bits...
[RAZR HD Android Development] elborak:
Oh, I completely agree. I also, however, have been here long enough to have had my expectations forcibly lowered. At least we haven't had any of the "where do I type these things" folks in this thread. :eek:

Completely understand. Everyone has to start somewhere, but at least show that you're trying to learn and not just repeatedly posting "now what's the next step?" and my personal favorite "these steps are confusing, post a video".

And thanks for your work on the radio issues. I've not been able to test your builds as, for some reason, every CM ROM I've tried to install since I updated to the kkbl (official or unofficial, not counting the ones that bootloop) has booted into a state where the network connects (either WiFi or 3G/LTE), but the Google services can't sync (i.e. the status icons stay orange). I've not had time to do much debugging of the problem, so I'm back to stock temporarily.
[RAZR HD Android Development] beefx:
must know :)

will 01.18 C’s build work if i just flash it in twrp 2.8.4.1 by dhacker?
[RAZR HD Android Development] CWGSM3VO:
It should, I removed the product check assertion.

EDIT: I lied, I removed it from 1-17 not 1-18, my bad.
[RAZR HD Android Development] Zeljko1234:
I just dirty flashed without removing anything.
[RAZR HD Android Development] beefx:
ok, downloading. last night i flashed PA alpha1 by cj360 with twrp 2841 and it booted fine.

So official cm12 not booted yet?
[RAZR HD Android Development] CWGSM3VO:
First boot on clean install can take upwards of 10 minutes, be patient. If after that it still hasn't booted, I'd be concerned. However, depending on the GApps you've installed, it could take longer. Usually I rely on adb logging to tell me whether or not it's booting or not.

Anyways, long story short, it can take a while for the first boot to complete.
[RAZR HD Android Development] beefx:
so it booted fine! Unfortunately, i get audio issue :(

loudly noise, screaming.. remembering? i get this problem only on your build now.
[RAZR HD Android Development] Zeljko1234:
See? Just kindly ask and something will happen. Otherwise he wouldn't know about problem at all.

https://twitter.com/dhacker29/status/557054829357707264
[RAZR HD Android Development] CWGSM3VO:
Yes, I remember the video you showed me of it doing that, I've never heard/seen it before. If it doesn't do it on a regular (official) nightly and only mine, then I must be doing something significantly different then they do :(

Can you repeat the same steps as you did in your video but logcat the entire process?

---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------

I'll test it, if it works, saves me time in the long run. Thank you DH.

EDIT: Got display first boot. Looking good.

EDIT: I forgot how awesome TWRP was. Backup works fine.

EDIT: It's actually 2.8.4.0 according to the version string btw.
[RAZR HD Android Development] KC69:
01/19 nightly is up on cm.
[RAZR HD Android Development] CWGSM3VO:
OK, so the TWRP that DHacker posted up works 10 out of 10 for me on display being active when entering recovery (ie: no black screen). Looks like we have a winner.
[RAZR HD Android Development] forserg:
hm, I flashed TWRP 2.8.4.0(xt926) no problem, but when I tried to flash 2.8.4.1 got message <bootloader>Variable not supported!

Used TWRP 2.8.4.0 to flash 1/19 nightly System UI has stopped.
[RAZR HD Android Development] CWGSM3VO:
The link in my sig is the link Z posted a few posts up. I flashed the xt925 version which was posted as 2.8.4.1 but the recovery itself shows 2.8.4.0 at the very top when you're in the main menu/settings/etc.

I just re-built 1-19 and it flashed it without any product assert (it installed fine) and gave the unusual 0.20000 as the success result.

It just booted no problem. Looking at my home screen after upgrade.
[RAZR HD Android Development] Raven2m:
Has anyone loaded it yet? I can't mess with my phone till later this week since I'm oncall for work ?
[RAZR HD Android Development] CWGSM3VO:
[MENTION=4869210]Raven2m[/MENTION] - the build I just flashed is a 1:1 with what you download, it should boot for you assuming your recovery will do it.
[RAZR HD Android Development] danfeng:
Just flashed TWRP 2841, got a message TWFunc Remove_MTP_Storage unable to locate partion for 0
[RAZR HD Android Development] Mikerhinos:
Been testing 1/11/2015 rild rom for a few days now, and still got same signal loss problems :confused:

Today I got up and phone told me that 3 updates are available : cm-12-20150112-NIGHTLY, 20150113 and 20150114, but as last time I totally messed up my phone by updating OTA "old" jbbl updates, I don't know if it's safe to update now lol.

Is there any rom that has a fix for signal loss ? (generally when I wake up screen I see signal bars go to zero, then a few seconds later the H sign disappear, then many seconds later it comes back and I have signal back. Like if radio crashes and restarts itself or something). I have bad signal at work, and am on Wifi at home.
[RAZR HD Android Development] Zeljko1234:
During flashing I got that too. Probably we can ignore that if MTP is not connected.

---------- Post added at 11:35 PM ---------- Previous post was at 10:39 PM ----------

jbbl user, check this http://review.cyanogenmod.org/#/c/86261/

Emerson is back :)
[RAZR HD Android Development] beefx:
i don’t know how do this :)
[RAZR HD Android Development] Zeljko1234:
You can do that from command line but probably the easiest way for you is to install logcat extreme, start recording and then do what you wish to capture log
[RAZR HD Android Development] Zeljko1234:
Nice new animation :)
[RAZR HD Android Development] lcc014:
I just flashed TWRP 2.8.4.0, rebooted 5 times and got black screen at the very first time after flashing. In 3rd time, I got some error in recovery. Something about mount partition 0. Could not get back to main menu, so I had to hard reboot by pressing the power and volume buttons at the same time. After that I had no issue to go into recovery and backup my "C's 20150111" image. TWRP recovery is cool; I have never used it before.

---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------

I got this message too but in the second try going into recovery. Then in 3rd try, it fixed itself.
[RAZR HD Android Development] Vnvjeep:
Got this same message on twrp 2.8.4.1 about MTP and partition 0, but ignored it. Also for the first time since being on 2.8.3.0 I've been experiencing the black screens by going into recovery... sometimes takes 2 times before it lets me in, just by rebooting back in recovery. Funny thing is, the screen seems to be responsive, because if you touch it, the phone vibrates like when you tap on a selection.

I have still not been able to load a copy of CM12 or Blisspop (1/19 versions), as they just sit there during the boot process, with the animations just keep going in circles. Any suggestions?

Thanks,

Mike
[RAZR HD Android Development] CWGSM3VO:
Try something newer like 1-19+
[RAZR HD Android Development] lcc014:
Would like to try; where is the 1-19+ ? :)
[RAZR HD Android Development] CWGSM3VO:
I like the old one better with the frowny CID :)

---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------

Follow links in my sig.. or... http://www.cmxlog.com/12/xt925/
[RAZR HD Android Development] lcc014:
Thanks :)

---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------

I am updating to 1/19 now, no bootlooping issue :good: I am using twrp 2.8.4.1 (actually is 2.8.4.0) recovery to clean install from SD card.
[RAZR HD Android Development] CWGSM3VO:
As Z noted (and yourself), you can ignore this, MTP isn't being used.

Try the old PhilZ workaround - swipe right-to-left twice, left-to-right twice and then try a volume button. That usually woke the screen up for me. But I've been having ridiculously awesome luck with this KKBL recovery, screen every time I enter it.

It can take a LONG time for the first boot of CM12 to load up from a *clean* wipe. If you've installed over top of CM11, you're on your own ;) Of course I could sound like a broken record and ask for logs, but adb seems to be a dying art (hah, made a punny...)
[RAZR HD Android Development] Zeljko1234:
I don't care about bootanimation. For me could be just something live to see that is not frozen. But old animation is really old, we're seeing it for too long.
[RAZR HD Android Development] CWGSM3VO:
I usually replace the bootanimation with the verizon droid one (y'know... DROOOOOID then the transformer thingy). Makes people go "oooh" when I show it off :p

EDIT: Looks something like this: https://www.youtube.com/watch?v=t8GLFSCqUis
[RAZR HD Android Development] KC69:
I ve gotten myself stuck. Xt926, 12/16 cm recovery, stuck in bootloop on Every ROM I've tried to flash. Can't flash a different recovery , they all fail. My PC is tied up by wife and kids. I dont know how to convert an IMG to a zip to try a newer cm recovery or twrp. Is there a way to convert these using a phone?
[RAZR HD Android Development] Zeljko1234:
Especially if you're in quite place DROOOOOID :D

I'm not sure that I have it anymore, so yes, you can upload it somewhere ;)
[RAZR HD Android Development] StefanGA:
I believe, these are the droids you are looking for => http://xdaforums.com/showthread.php?t=2366956
[RAZR HD Android Development] djvita:
had bootloop wiht 1/19 blispop im gonna try 1/20 cm12 back to here then, while the bliss team figures out whats up

left for 20 min cm12 1/20 nightly still bootloop. using latest twrp for xt925 linked in dhacker29's twitter.
[RAZR HD Android Development] CWGSM3VO:
Yup, that's the one I use :) Thanks.
[RAZR HD Android Development] ovar:
Have a xt926. Clean installed the 1/20 nightly and PA Pico Gapps for 5.0.1.

Was having a lot of issues with screens freezing. First it started with settings screens and then almost every other screen I opened. Home button would randomly not work. Are there any tips to getting L to run any smoother on the XT926? Are others having issues?
[RAZR HD Android Development] CWGSM3VO:
Try DH's 12-20 Gapps, see link in my sig. Let the play store update as it sees fit. Problem with PA GApps is they try to be everything to everyone rather than being as agnostic as possible. Not that this is a bad thing, but using "known good" software versus "latest-n-greatest" may help you isolate the issue.

That's my recommendation.
[RAZR HD Android Development] Zeljko1234:
Maybe you just caught not so stable nightly. Currently I'm using C's build from 1/18 and don't have issues you mentioned. Actually I dirty flashed over previous build. The biggest issue I have is with BT. Previous build was freezing, sleep to death, etc if I use HRM and BT headset. To be honest, didn't try 1/18 with the same BT combination (raining outside for running) but didn't see any commit related to fix BT.
[RAZR HD Android Development] Zeljko1234:
Looks that I found workaround for my BT problem. First pair headset, start playing music, then start sport tracker with BLE HRM. Worked for few songs without any problems. Will test tomorrow with GPS.
[RAZR HD Android Development] tripaX8:
The only way I got rid of bootloops in CM12 1/20 was by flashing and booting CM11 before CM12. (without doing a factory reset).

Using same TWRP as you did.

Hope this helps

EDIT: Someone told me that had no bootloops with a clean flash of CM12 (1/20), the only difference was that he had ext2 formatted data, instead of f2fs, maybe that's the key. Will try that, can anyone confirm ?
[RAZR HD Android Development] djvita:
I tried f2fs and ext4 same result bootloop so you suggest dirty flash cm12 above 11? Will try tomorrow
[RAZR HD Android Development] Mikerhinos:
Just dirty flashed nightly 01/20 with gapps on top of the C's rild tweaked rom, for now no bootloop or any other problems, just booted fine.

Will test it all day at work (where I have bad signal and many loss problems).

Used TWRP from C's sig because my "old" CWM gave status 7 error when trying to flash.
[RAZR HD Android Development] MaicolS:
Hi, sorry if this question is a little OT but does anyone experienced or know how to solve blue blinking screen after switching apps? I'm having that since first cm12 xt925 specific build and now i'm at 1/19 of DH builds

Greetings, Maicol
[RAZR HD Android Development] kabaldan:
It should be already fixed by this commit: https://github.com/CyanogenMod/andr...mmit/ff994867db2e2051e4db064d733b8462b2fc52bf

Not sure what you mean by "1/19 of DH builds", but the fix is present in official CM nightlies since 20150119:

http://download.cyanogenmod.org/?device=xt925
[RAZR HD Android Development] CWGSM3VO:
I find it strange that a user has the blue flicker problem yet I've never seen it since early CM12 and since early 4.3 -- I understand there's differences between the XT925 and XT926 but is there really that much variance between XT925 models as well? I know the Australian XT925 has a different compass/magnometer chip than mine but those were the only differences I could find within the same model. As far as I know, the only way to repro the blue flicker was to enable "disable h/w overlay" although the commit refers to framebuffer depth(?) being the cause.

Just trying to wrap my head around why a one person would have blue flickering and one wouldn't running pretty much the same hardware and software.
[RAZR HD Android Development] Zeljko1234:
Maybe because of board/chip(set) revision? We had similar problems with Atrix kernel. Few revisions of memory, etc. Causing problems for some and when is fixed for them, causing problems for others. For example we had screen out of sync, like old CRT TV. Rarz is still much better of that.
[RAZR HD Android Development] CWGSM3VO:
Makes sense in "computer" terms (to me) but these are mass-produced devices right? Other than some regional differences (ie; radio or compass) they should all basically be the same device you'd think.

Ah well.
[RAZR HD Android Development] Zeljko1234:
Unfortunately no. Usually every device has few revisions. Sometimes because of solving hardware bugs, sometimes because of lack of parts (chips, displays, etc. I remember first HTC Desire, started with AMOLED and switched to LCD later), sometimes chip vendor make a new revision... I would say that makes even more sense for mass-produced devices as smartphones than for for example, motherboards or laptops. HP laptops are good example, hell to find proper driver for "the same" model.
[RAZR HD Android Development] KC69:
Still boot looping. Taking a crash course on adb/fastboot. Trying to get past device not found and how to enable USB debugging from ap fastboot. Using cm recovery 01/16. Can't get away from it. It won't let me flash any other recovery. Pissing me off. Been having to use my nonrooted M backup phone. Sux to be me.