yashsingh1/xdaforums huggingface dataset:
[RAZR HD Android Development] Pow_2k:
If v6.57.5 "hangs" on load, BE CAREFUL!!!

Wondering if I'm getting the same "hang" as you... On KK with PhilZ 6.57.5. Attempt to reboot to recovery (I'm using Quick Boot, but I've seen the same from the "3 finger" menu), the the red M then black screen. Need to hold down power button to reboot as normal. Hit and miss for me if I get into recover or get left at the black screen. Haven't been able to find a pattern yet.

The problem does simply seem to be that the display isn't showing up. PhilZ Touch is actually loading but you just don't see anything.

AS SUCH BE VERY CAREFUL WITH WHAT YOU PRESS WHILE "HUNG" TRYING TO GET TO RECOVERY!!!

At one time trying to get this to reboot I managed to wipe my external SD card. Luckily I didn't have anything on it but images/ROMs I still also had on my computer so just an inconvenience. It could though have been much worse. My proof of concept to show that PhilZ is loading and simply no display:

Attempt to boot to recovery via method of choice.

After the Motorola logo (round red M) you get PhilZ, reboot and try again.

If after the Motorola logo you get a blank screen and you are running PhilZ Touch v6.57.5 (just in case diff versions have diff options), press the following buttons in this order and nothing else!

Volume Up

Power

Volume Down

Power

Welcome to the bootloader! If PhilZ had been showing up on the screen that series of buttons would have seen you wrap the selection from top to bottom to select "Power Options" followed by moving the selection down one spot on that menu to select "Reboot to Bootloader". If you omit the Volume Down keypress you can instead try to reboot to recovery. Again, still hit and miss as to if PhilZ displays.
[RAZR HD Android Development] KrisM22:
yuh know guys, reading this is very scary........... :(
[RAZR HD Android Development] Pow_2k:
I tried to make it less scary once I found others may have had the same "hang" as me but providing my findings so it can still safely be used. Yeah, I'd like to see if it can be fixed but I don't intend to stop using PhilZ in the meantime. Might try some prior builds tho...
[RAZR HD Android Development] KrisM22:
LOL yes, I know you tried. at this point I'm lucky as I'm still on jbbl. But I watch this as this is where I expect I'll be in maybe a month. Scary!
[RAZR HD Android Development] Pow_2k:
FYI, it appears the moto_msm8960 build of PhilZ may not be the only group of devices that experience the "blackout". See the main thread starting with post #5392 by chautruongthinh:

http://xdaforums.com/showthread.php?p=55318656#post55318656

And their fix for it discussed starting with post #5465:

http://xdaforums.com/showthread.php?p=55464982#post55464982

Broken brightness path in the kernel? Not sure how this would be resolved for moto_msm8960 or if the problem is even the same, certainly well over my head. Certainly looks similar but I can't tell if it is just the blacklight not turning on. No matter what light I shine into the phone at what angle I can't tell if there are any pixels set.

---------- Post added at 12:00 PM ---------- Previous post was at 11:19 AM ----------

Additional find... when you are able to load PhilZ Touch in a visible mode go into Recovery Settings/GUI Preferences/Gesture Action Setup. Confirm if you have any actions set to "toggle screen". For mine the default was slide left, I assume that would be the case for all. Also confirm in the GUI Preferences that you have the Menu Height option set to something that still leaves empty space below the main menu (I'm using 78 and the main menu only takes up about 1/2 the screen). If you boot to recovery and get the blank screen, in what would be the empty part of the main screen where there would be no buttons you can use the gesture action twice. This will first toggle the screen off, then toggle it back on. This brings up PhilZ as it should have been shown in the first place.

Might still be good to familiarize yourself with where the "back" touch button is. In the event you get into blackout mode PhilZ and don't know if you've entered into one of the sub menus already it seems to be safe to keep pressing the back button a number of times to ensure you're at the main menu. Then you know you've got space to use a gesture action providing you don't have the menu sizing set to fill the screen.
[RAZR HD Android Development] muccioli:
Could someone explain how to use the philz to root the xt925 4.4.2 180.46.117?

I tink to choose the option "install .zip"? Well, Where i find the files to root?

Thank you
[RAZR HD Android Development] ryankliber:
I had blackouts with regular cwm recovery when I switched to the new bootloader. Went to twrp after a few days and haven't had a single problem getting into recovery since.
[RAZR HD Android Development] Pow_2k:
Thanks for confirming the problem existed in CWM as well. Don't recall if I had seen that or not. With PhilZ Touch being built on CWM it isn't surprising.

Unfortunately PhilZ has put his flavor of the recovery to rest due to other priorities. From his post it also sounds like CWM itself is at a stop as well? http://xdaforums.com/showthread.php?p=55600060

Guess it may be time to re-examine TWRP. Bummer as I really liked PhilZ Touch for my devices.
[RAZR HD Android Development] Phil3759:
probably just a kernel update needed

CM kernels suck in that regard as CWM is no longer maintained. When maintainers push device updates, they quiet never take recovery into account

You could just compile with stock or Omni prebuilt kernel. Chances are it will fix your issue
[RAZR HD Android Development] palmbeach05:
Any chance those of us on a jbbl could get an update?

Sent from my MB886 CM10.2/4.3.1
[RAZR HD Android Development] KrisM22:
fwiw, cwm 6.0.5.1 swipable touch for msm8960 JBBL is available here

http://xdaforums.com/atrix-hd/development/recovery-cwm-6-0-5-1-jbbl-t2891842

Extracted from CM11 JBBL nightly by [MENTION=4895937]palmbeach05[/MENTION]
[RAZR HD Android Development] CWGSM3VO:
Swung by this thread again and saw this. I too have similar issues with blackouts. Usually second reboot into recovery works for me. I suspect once I get the "proper" KKBL flashed from my carrier, it might go away. I suppose I could give TWRP a try but I really like this recovery.
[RAZR HD Android Development] hbenz2008:
TWRP does the job. 7.1.0
[RAZR HD Android Development] SCFirefighter:
I bumped into something interesting:

I'm running Orphee's latest Philz build, and it still blacks out on me most of the time.

However, I found a default gesture that works for me.

When you're in a blacked out Philz recovery, swipe left twice.

Once will toggle your screen off, (even though it's already off), and the second time you'll see your screen pop on instantly. Check out the setting in the screenshot.

Thoughts?
[RAZR HD Android Development] Pow_2k:
Yep, post #229 in this thread. [emoji4]
[RAZR HD Android Development] SCFirefighter:
Dammit! Sorry. Missed it. There go my 15 seconds of internet fame :D
[RAZR HD Android Development] Phil3759:
I am updating sources to try to fix it

Seems it is related to dim screen

If you disable dim screen timer, it should fix it
[RAZR HD Android Development] CWGSM3VO:
Think this might be related to the blackscreen boots into recovery, or at least, it has the same affect:

http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2800-09-14-14/

Granted it's TWRP but ...
[RAZR HD Android Development] Pow_2k:
[MENTION=813614]Orphee[/MENTION] (or anyone else with the tools/knowledge to do so), would you be kind enough to rebuild PhilZ Touch for our device? The 6.58.0 (libtouch_gui 1.42) sources have been updated with a screen dim fix that may resolve the blackout we've seen on our devices. Phil's post here: http://xdaforums.com/showpost.php?p=55842367&postcount=5567

Take note, there was a warning posted in the thread later on that I'm not sure how it relates. If someone wants to educate me I'd be welcome for input. http://xdaforums.com/showpost.php?p=55937534&postcount=5583

TIA to anyone who builds and shares the update!
[RAZR HD Android Development] Orphee:
I'll see if i can do it in the week end
[RAZR HD Android Development] Pow_2k:
Orphee, first thanks for taking on the build. Second, if you haven't noticed Phil put an update out that I think covers the repo warning I previously linked to but don't understand. :). Just a heads up!
[RAZR HD Android Development] Phil3759:
yes, it fixes build issues with latest sources
[RAZR HD Android Development] Orphee:
I just built latest Philz Touch Recovery with F2FS support : http://d-h.st/3uo

Be carefull, I did not try it. It is untested.
[RAZR HD Android Development] MCP1:
Thanks Orphee!

It seems fine. No blackouts after a few reboots.
[RAZR HD Android Development] Orphee:
I just built 6.58.7 with F2FS support : http://d-h.st/Lar
[RAZR HD Android Development] Pow_2k:
Weird... I just installed the 6.58.7 build from Orphee and I'm still getting hit-n-miss blackouts on my XT926M. One thing I noticed changed is I can no longer left-swipe twice to get the screen to come on. But, if I left-swipe once and then press the "back" screen button (just above the location of the "on" of Verizon on my display) the screen will come up. I had whacked my settings save files (internal and external) to confirm it wasn't something from my old setup causing a problem. Oh well, thanks for trying guys.

An observation worth noting... pressing the onscreen back button always seems to return you to the first option of the prior menu. So multiple presses will get you to the "reboot now" option on the main screen, where it would then be safe to press the power button and exit.
[RAZR HD Android Development] Phil3759:
some devices do not properly support brightness and screen off

Just disable them in settings maybe

It is probably a kernel issue. Since I do not own the device, I am not going to look at the kernel and fix it. Live with it or get someone to repack it with a stock kernel. Maybe later, cm update sources and the kernel gets fixed
[RAZR HD Android Development] Pow_2k:
Giving that a try, but so far not a fix. Found the dim and screen off settings, not sure what to do if anything for the "set brightness" one. Previously when the screen would come up it did properly dim and then switch off when I had it at defaults (1 min, 3 min) and in my last test did come back up with a touch. Don't recall if that was in the "back" button area or not. With these now disabled it doesn't dim or turn off, but it also isn't a guarantee display on boot into recovery.

For anyone that can't seem to load this up and wants to try manually putting these settings in place, the line entries to insert into philz-touch_6.sav are:

dim_timout=0

blank_timeout=0

These were entered into my config file when I set the dim and screen off settings to disabled via the PhilZ Touch GUI settings.

Yep, I know. :) There's a whole lot out there that can't be directly tested. Appreciate that you still took the time to put a couple updates in your sources even after you (tried to, unsuccessfully) retire from the project. As I have been doing I'll just keep trying to deal with it until a fixed build comes along. I've tried TWRP 2.8.0.0 (found over at droidrzr.com) and it seems that doesn't have any blackout issues but the organization of options in PhilZ Touch seems much more intuitive to me.
[RAZR HD Android Development] swapyworld:
Need help

1. using xt926m, i am on rooted and unlocked KK, which version should i flash?

2. If i downgrade to stock Jb, can i continue using the latest recovery or do i need to flash an old one?
[RAZR HD Android Development] palmbeach05:
If the recovery is designed for JBBL, and you have JBBL on your device, you flash it. If the recovery is designed for KKBL, and you have KKBL on your device, you flash

I refer you to page 21 of this thread for the final JBBL recovery.
[RAZR HD Android Development] swapyworld:
it says 6.48 is the last one for JBBL

so i guess i can flash 6.43.6 (02.06.2014) listed in OP....right?
[RAZR HD Android Development] KrisM22:
FOR JBBL: at last check, 6.48 does not restore it's own nandroid backups. so 6.43 would be a better bet if you are going PT.

FOR JBBL: 6.0.5.1 CWM swipable touch is available here:

http://xdaforums.com/atrix-hd/development/recovery-cwm-6-0-5-1-jbbl-t2891842
[RAZR HD Android Development] spinninbsod:
Will this work on atrix HD I used to have an atrix HD but it was a long time ago so I'm a bit confused ☺
[RAZR HD Android Development] KrisM22:
meditate on the post above yours.

meditate on the sig of that post.
[RAZR HD Android Development] IronTechmonkey:
ROTFL Well put.

... and here I am considering upgrading my version of PT since the old one I'm using cannot flash arrrghhh's anykernel. As ever thanks for the tips which I appreciate through mediation or direct conversation.
[RAZR HD Android Development] spinninbsod:
Okay I just figured it out the jbbl version works on the atrix hd
[RAZR HD Android Development] KrisM22:
hey! Go for it!!! They're cheap!!! :D:D:D
[RAZR HD Android Development] IronTechmonkey:
And of course I meant meditation rather than mediation but that's a pretty good typo.
[RAZR HD Android Development] KrisM22:
:D
[RAZR HD Android Development] KrisM22:
I ran 6.43.8 for a while with no problems. I also notice I have 6.43.4 and .6 though I can't remember if I used them. At that time I just tended to grab the latest... :D

avoid 6.48
[RAZR HD Android Development] IronTechmonkey:
I went with the newest unified one from the OP, that being v6.43.6, and have been able to restore recent backups as well as flash nightly and anykernel. Thanks!
[RAZR HD Android Development] hachamacha:
Hi,

I guess I started this thread and need to get up to date on what's up. I kind of stopped when Phil declared his recovery development basically ended a few months back. It's at version 6.58.7 lately. I've built versions for most of the other devices I supported and they seem good.

First: Didn't someone take this development over for the 4.4.4 msm's? If so, they should probably carry on here. If not, then I can do an msm build, leave it at the thread end and if you tell me it works, then I'll leave it in the OP.

2nd: Which OS version are you guys using these days. Are you having troubles? Can you supply logs?

3rd: I can't test the device anymore. Don't have it, so testing would be on you.

Anyway - a few things to think about:

Cheers.
[RAZR HD Android Development] hachamacha:
Test version 6.58.7

This version, if it works at all, will likely only be of use with 4.4.4 KK versions. I'll just supply a link to the image made from the latest cm11 base code and Philz latest:

Note: I hope it works for some of you. If not, just reflash the last working one however you've been flashing.

Note 2: Put in OP.
[RAZR HD Android Development] Phil3759:
Will upload to goo

Thanks
[RAZR HD Android Development] hachamacha:
Thanks [MENTION=4666971]Phil3759[/MENTION]:

Also: I lost track of where the msm8960 updates had gone, and for some reason thought that 4.4.4 update had come out in OTA's , had been done in soak tests, etc. Looking around, I might be off by a couple versions. I think wherever it says 4.4.4 , I should have put >= 4.4.2. I'll fix that up when I confirm.

Oops.
[RAZR HD Android Development] palmbeach05:
I'm going to guess that from the wording of what you said, this is KKBL only?
[RAZR HD Android Development] hachamacha:
Yes, based on what I'm seeing in cm11 (the base I build from), it should work on KK BL.
[RAZR HD Android Development] KC69:
Will this work with ROM manager or ROM toolbox?
[RAZR HD Android Development] Any PlayStore:
Thanks
[RAZR HD Android Development] djvita:
always used cwm. now flashed 6.58.7

in my device its all green hues and the touch doesnt work
[RAZR HD Android Development] KrisM22:
I believe 6.58.7 is for KKBL only...
[RAZR HD Android Development] robobub:
EDIT: I see the latest only works on KBBL.

If anyone has any ideas on why F2FS isn't working for me on JBBL, I've documented my struggle here:

http://xdaforums.com/showpost.php?p=56704552&postcount=5316
[RAZR HD Android Development] KrisM22:
I believe f2fs is only supported on KK - 4.4.2,3,4
[RAZR HD Android Development] RMarques:
Hey there guys, can anyone enlighten my toasted brain about why I cant flash DHacker CM12 nightlies for Razr HD no more since I attempted to format my /data to F2FS? It was working ok before!

Even formatting it back to EXT4 I always ended up stuck at the installation process...both in TWRP 2810 as well as Philz 6587!
[RAZR HD Android Development] Zeljko1234:
What kind of error you get?
[RAZR HD Android Development] RMarques:
Thanks Zel,

I'm not home now, I'll post some screenshots errors in a while when I get there.

Sometimes there isn't any route messages at all...It just gets stuck at the installation animation forever.

I was being able to install all cm12 no problems until I tried to format /data to F2FS.

Sent from my RAZR HD using Xparent Skyblue Tapatalk 2
[RAZR HD Android Development] Pow_2k:
This is from a completely unrelated thread, but I'm thinking it is a clue. (Sero 7 pro tablet, dopa ROM, philz touch)

* install the ROM - if you're using f2fs, ignore any errors reporting that a partition couldn't be mounted

So I'm wondering if the install script isn't set up to mount f2fs partitions?
[RAZR HD Android Development] hobbit19:
pls update version
[RAZR HD Android Development] KrisM22:
Did you sus this one? like by flashing the Orphees version of KK6.58.7 that CWGSM3VO is using? (which is different from the one here.) see post 227 on lollipop thread... KKBL only.
[RAZR HD Android Development] palmbeach05:
Please install CWM from CM and see that you will experience the same thing on both. Only difference is the philz touch experience. Plus, philztouch is discontinued.
[RAZR HD Android Development] sobitthen:
Instructions for .zip, how-to for .img?

I was told I needed to update my recovery to the last Philz if I were to use the Gapps packages.

The instructions for the module has instructions for flashing a zip file but the 6.43.8 I was going to load for my Atrix HD is in an img format, are there different instructions for flashing this file, can it just be zipped, thought that to be too easy...
[RAZR HD Android Development] Pow_2k:
You can try flashing an IMG via an app like Flashify or Rashr, or go lower level and use either adb or fastboot.

EDIT:

A minor correction, I had things mixed up and you can't flash a recovery with *just* adb. But I was curious and did some digging, found that you can use "flash_image" via an adb shell to flash a recovery. There may be other similar methods but once I found this "yeah, it is possible" answer I felt satisfied and stopped looking. Find the directions in the "manual methods" section of this page.
[RAZR HD Android Development] palmbeach05:
Fastboot flash recovery *insert-file-name-here.img* is too hard for you?
[RAZR HD Android Development] CWGSM3VO:
Good helping, bad delivery.
[RAZR HD Android Development] sobitthen:
Thanks, I had found and used the Flashify last night and flashed the required image file.

And to the other, yes it was too hard for me as I had forgotten, all these narcotics for my broken back have my mind in limbo most of the day, so I rely on the forums and research to get most things like this done, I had looked for an hour then resorted to asking a question...
[RAZR HD Android Development] dbmiller5:
edit:delete
[RAZR HD Android Development] palmbeach05:
....or we could actually look through the thread and go to page 27 instead......
[RAZR HD Android Development] dbmiller5:
The recovery seems to work great except for one issue I have run in to.

With 6.58.7: "adb sideload" does not work, in fact adb does not recognize the device when I do "adb devices". When I go back to the standard 6.0.5.1, sideload and adb in general works normal. I am sticking with CWM 6.0.5.1 for now because I like to use sideload.
[RAZR HD Android Development] palmbeach05:
That goes back to the issues philz was having with all these devices and why pt is discontinued
[RAZR HD Android Development] dbmiller5:
Good to know! +1
[RAZR HD Android Development] CWGSM3VO:
Nice thread, been following it. Interested in the idea of backing up/restoring the persist partition (or even extended to support other device-critical partitions). Would save new users a lot of headache if someone can, in the future, provide them with a "stock" image to recover easily from rather than going through the whole SBF business.

Really digging this recovery. Find new stuff every time I use it.
[RAZR HD Android Development] hachamacha:
Thanks.

I think there's another source update, but there was also one yesterday. I did a couple builds a) the usual vanilla build for msm8960 and b) a test build that should be able to at least backup /persist. There are some flags in CWM that inhibit the ability to restore or format the /persist partition, so probably at some risk, I yanked out ", /persist", /next.. from that list of prohibited actions. I'm going to test the basic functionality of both before uploading and updating this thread but want to stare at that code a bit more before killing my phone by testing the /persist restore (if it even shows up) ;)

In this iteration the partition for /persist may show up as /extra_part5 since that is 'built-in' expansion stuff that doesn't require me to veer completely off course, just a name anyways. Since you can mount and see /persist in aroma, you can tell what files are correct to be in /extra_part5. Anyway, got a bunch of stuff to do today so it'll be a bit later on like by tomorrow hopefully.

Re: Aroma working: I'm not sure that's much of a sign since it pretty well does it's own thing and appears to be one size fits all. I always build it as part of the recovery build but don't usually bother putting a link to it since I'm not able to see what difference it makes using mine or the one from the Aroma guy. The 907 has the difference resolution and a few other differences, which are actually unified OK in cm11, but it's not clear to me that this recovery is yet taking it into account. Isn't there also some 'switch' in the recovery for using screen/other-choice/keys?

Maybe I'll make a 2nd test build for the 907 with the specific resolution and see what happens. I can't imagine the touch working if I'm basically only building for the HD res and merging them isn't yet there.
[RAZR HD Android Development] CWGSM3VO:
Dunno if anyone noticed but I flashed 6.22.7 and the version I see on first boot is 6.22.9 :) Op states 6.22.7 is the actual version rather than 6.22.5; might have missed this earlier in the thread.

---------- Post added at 10:39 AM ---------- Previous post was at 10:27 AM ----------

One request... I noticed over in the CM11 thread that some people switching to PhilZ have issues with the CM11 OTA upgrade method. This is because the default InternalSD setting in PhilZ Advanced Settings (SDcard target) is set to /data/media/0 instead of /data/media (for XT925 anyways, probably all moto_msm8960).

Once configured to the latter, the CM11 OTA upgrade process works flawlessly. Can this be set to /data/media as default? Better user-experience so to speak ;) Or are there any use-cases where this would break the majority vs the minority?
[RAZR HD Android Development] Phil3759:
Read the faq please, cmupdater section. I do not plan to revert to their non sense implementation
[RAZR HD Android Development] CWGSM3VO:
Missed this part, I discovered it without reading the FAQ but there it is. I'll make sure to point people there in the future, thanks for steering me in the right direction.

EDIT: Linking for future readers: http://xdaforums.com/showpost.php?p=43707326&postcount=8
[RAZR HD Android Development] hachamacha:
Oops. Sorry about that. I read it in the github code and then totally forgot about it when I built after the changes ;) I'll fix it up when I post the next update.
[RAZR HD Android Development] aviwdoowks:
Note on aroma

It never worked before (was key only) when started from non 907 philz.