Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Addendum: Unified builds, in particular this one for moto_msm8960 devices:
Supposed list of unified devices: Previous RAZR HD, Photon Q, Atrix HD, etc. : xt897, xt901, xt905, xt907, xt905, xt925, xt926, mb886 are now:
Now: moto_msm8960
I'm going to put them in a list so I can get around to checking Y on known working ones, and N on known non-working ones:
- xt926 (Y)
- xt925 (Y)
- mb886 (Y)
- xt897 (Y)
- xt901 (?)
- xt905 (?)
- xt907 (Y)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Quick notes about unified devices:
Do they all work in this build? I have no idea, but am pretty sure that from feedback that xt926/5, xt907 and xt897 have been reported to work.
The bottom line is that I rely on anyone reading here (or who is directed here from their development pages) to let me know what works, what doesn't so please let me know.
----------------------------
Download links
Latest versions built by me can be found here: (currently 6.xx.* and up).
Note: 6.58.7 final/stable is the latest (see the main development thread if not understood)
Changelogs:
v6.58.7 - new code and fixes
Click to expand...
Click to collapse
6.43.6 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 - Final, Stable
- fix text print color could persist after md5 check
6.42.9 - Final & Stable
- default again to libtar for backup/restore
6.42.7 - Stable
- default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.41.6 - Stable & perhaps Final
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Click to expand...
Click to collapse
- Unified msm8960: 6.58.7 (4.4.4): Image : http://d-h.st/2xD
- v6.43.6: Unified msm8960: http://d-h.st/HgH
- v6.43.4: Unified msm8960: http://d-h.st/sQQ
- v6.42.9: Unified msm8960: http://d-h.st/SjY
- v6.42.7: Unified msm8960: http://d-h.st/9pD
- v6.41.6: Unified msm8960: http://d-h.st/uq1
- v6.41.5: Unified msm8960: http://d-h.st/QiK
Click to expand...
Click to collapse
Note: tested only on my xt926. Aroma has a few little glitches but is not often maintained.
Older versions built by Phil (or his 'crew'):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt926 // oldest (and substitute your dev name for pre-unified builds)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960 // newer, recent.
Click to expand...
Click to collapse
My github(just created/work-in-progress) for tracking changes on this: https://github.com/Hachamacha/philz.git
Click to expand...
Click to collapse
Note: My part in this is very minuscule. I just got (git) his source and stuck it into cm11 as a build base. I changed very little, only added the msm8960 build since I think phil is working on the source rather than many individual builds due to time. If you look at his github from the main page link, the only file I really changed was ./boardconfig/BoardConfig.mk under ./recovery.
Goal: Just to make this available and keep people out of the main thread that aren't developing. If I can help with the specific device I'd do it, but I'm really not an xt926/5 expert. Still, if you've got msm8960 questions (so: device-specific, not general philz touch) ask them here about the device and recovery since odds are better you'll get an answer here than in the main thread. I'll try to update this with latest builds each week.
Disclaimer: The usual stuff you read in all of these threads. If your mind turns into margarine after installation, please send a sample to the CDC labs in Virginia. I searched all over XDA for a thread for philz for the msm8960 but didn't find it. If you do, feel free to destroy this thread, call me names, threaten my relatives (please do this), etc.
Credits: I think all credit should go to Phil, @Orphee and the CM11 guys if you like this type of recovery.
Thanks for doing this bro. Otherwise AHD'd be on 6.0.7x..
EDIT: Great job, I can confirm, 6.22.1 flashes and screen touches work perfect, format, wipe clean new rom, install new rom, restore backup on the Atrix HD/mb886.
Who wouldn't like the best recovery of all? Right? Thanks a lot
Works with keys only on the 907. Thanks.
aviwdoowks said:
Works with keys only on the 907. Thanks.
Click to expand...
Click to collapse
I don't recall the xt907 being unified into the msm8960, at least not in the philz code, but I could be wrong. Could you try a recent (6.19.x) build from over here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt907 and let me know if that works? I think the msm8960 so-called unified builds are still a bit confused. It looks to me like only xt926 and 5 are covered.
If the build I linked to works, then it's to do with the 'unified' setup and I might need to grab some vender ID's etc.
By saying "works with keys only": I assume you're saying that the touchscreen stuff is off-kilter or just off period?
Thanks and I'll look it over for that device.
Everyone else: Glad it's working out for you. I'll update as soon as there's another git update.
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
aviwdoowks said:
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Click to expand...
Click to collapse
Took a look at the cm11 base I'm using as a building platform for philz code and it appears xt907 isn't yet part of the unified group though it ought to be according to CM. I'll leave a note and see if that's in the works. I'll check if xt907 has it's own build over there. By the way, from your reply I wasn't sure if you'd tried the pre-unified version I linked to on goo.im? Also philz stuff is using his own touch library GUI these days, and there might be something about that and the 907. Got some stuff to figure out.
Looks like (Atrix HD, Electrify M, Photon Q, Razr HD, and Razr M) are supposed to be part of it but from the way the code looks, (boardconfig) , not sure I believe it's yet been worked out. Razr M has some 9xx x {?} resolution, right?
Edit: CM11 looks fine as far as unified for xt907, so it must be something in the philz code that's not yet ready for the full array of unified devices.
penser said:
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
I've used TWRP and like it a lot, but haven't looked at the build requirements yet. It seems possible to do unified builds for anything especially if you can do something like build the cm11 default code with it's default recovery, then substitute TWRP recovery for the default CWM in the ./bootable/recovery code. TWRP would have to be setup for that which is something I don't know. CM11 is where the unified structure is coming from in the case of these recoveries.
The 6221 you posted works.
aviwdoowks said:
The 6221 you posted works.
Click to expand...
Click to collapse
Cool! Thanks for letting me know.
hachamacha said:
Cool! Thanks for letting me know.
Click to expand...
Click to collapse
Are you savvy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
---------- Post added at 10:17 AM ---------- Previous post was at 09:41 AM ----------
More on persist
http://forum.xda-developers.com/showthread.php?t=2589790
aviwdoowks said:
Are you savy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
Click to expand...
Click to collapse
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Mount is ok. When I posted the now unavailable format was there.
aviwdoowks said:
Mount is ok. When I posted the now unavailable format was there.
Click to expand...
Click to collapse
I'm trying to reopen the discussion in the main thread so we'll see how that goes.
Edit: General build update.
There's a new build, same version but some fixes that I'll put up eventually here. CM11 probably has the newest API and I'm restructuring my environment, so need to sync and clobber repo, include philz as a localrepo. Might take .. all day for the syncing and building to complete. Doing this in a VM today
Fixed: Aroma now works with screen input when booted from the msm version while key only from philz.
Translation: aroma works fully while using this on a 907.
hachamacha said:
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Click to expand...
Click to collapse
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Phil3759 said:
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Click to expand...
Click to collapse
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
hachamacha said:
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
Click to expand...
Click to collapse
also, take a look here, at the highlighted line:
https://github.com/CyanogenMod/andr...8960/blob/cm-11.0/device_moto_msm8960.mk#L121
You have also a ro property to forbid mount:
Code:
ro.cwm.forbid_mount
Both these properties affect the format/mount options in "Mounts and Storage" menu
As far as screen input for the 907 goes, are you not almost there if aroma works?
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
It works on 6227.
Related
I take no credit for this, just passing information on for others to use. YMMV, use at your own risk..
roebeet pointed this out in irc;
SOURCE: http://notioninkhacks.com/forums/viewtopic.php?f=29&t=891
by StephenH » Wed Feb 16, 2011 1:58 pm
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
download:
Code:
Please refer to original post linked above for download link
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Click to expand...
Click to collapse
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is probably because there aren't very many Adam users yet.
keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.
rothnic said:
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.
Click to expand...
Click to collapse
They don't seem so keen on sharing huh? Interesting since they like to use other people's open source code...
Guess I will have to join in and start hounding them about it.
Sent from my ADR6300 using XDA App
keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
I second that. Am a fervent flasher (the right kind....) and when I get my Adam I will certainly be putting my own 2 cents in to get the most out of it, both OS and UI wise.
I am not alone, so definitely expect a flury of activity by Adam enthousiasts once the next 2 batches are delivered.
Sent from my HTC Desire using XDA App
You guys are lucky to have djsteve as your new Dev. He's put in a lot of work for the Dell Streak since it first came out and he will probably put in a lot of work for the Adam ink as well.
football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
I get mine tommorrow so I'm very excited.. will def try this
sent from gv1.5 on g2
Update: 10/03/2011:
UPDATE: 10/03/2011:
time for another update
changelog:
reverted vold change as it screws up things
added some more perf tweaks,
added data2ext script from gtab forum on xda, seems to work nicely, can hit quadrant scores of ~3200 now
flash you will need to install yourself at moment, i forgot to readd it link for flash : http://forum.xda-developers.com/showpos ... stcount=26
Code:
refer to original thread/forum for download links
enjoy folks and if anyone wants to do another video feel free.
---------------
UPDATE: 17/02/2011:
ok have tweaked a bit more and made a few more changes.
changelog:
new vold added with ntfs mount support (see below for some issues known with this)
flash player added and should auto install
fixed market and facebook
fixed superuser ability
added estrongs file manger for root use
tweaked the ril scripts to be easier to use.
added modified nvrm_daemon to increase 2d framerate
Code:
refer to original thread/forum for download links
*note for VOLD, this now mounts ntfs drives read only, but it has slightly screwed up the mounts, if you power up device with no microsd plugged in it will mount the internal storage and allow access to is via usb, if you plug in a microsd or boot with one in it will mount both internal and external sds but share the external over usb, it quite happily detects and mounts my 1tb usb hdd which is ntfs formatted though now.
ril tweaks: now all you need to do is create a empty file on your memory card called riloff.txt then reboot and script should do the rest to reenable rename the file rilon.txt and reboot
enjoy folks and if anyone wants to do another video feel free.
-----------------------
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
Code:
refer to original thread/forum for download links
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Last edited by StephenH on Thu Mar 10, 2011 6:15 pm, edited 2 times in total.
Click to expand...
Click to collapse
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?
mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?
EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!
mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build
negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.
Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
See device specific install instructions
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device Specifics
Install Instructions:
Unlock your bootloader
Follow these instructions
Credits:
@m11kkaa - for the pointer about kernel dt
@JackpotClavin - for the easier patch for touchscreen
Confirmed to work on XT1021, XT1022, XT1023
Latest Unofficial Download Here
kernel source
Device Tree
Changelog:
TWRP 2.7.2.0 V2.2
bump to V2.7.2.0
built against TWRP internal trees
TWRP 2.7.1.0 V2.1
bump to V2.7.1.0
TWRP 2.7.0.0 V2.0
touch bug fixed
backlight bug fixed
built against the latest caf kk_3.5 rb head (unreleased yet. I'll push it tomorrow hopefully)
TWRP 2.7.0.0 V1.2
Fix external SD mounting (I've only just found my card)
Remove unnecessary partitions from the mounting menu
TWRP 2.7.0.0 V1.1
Add dt kernel, allows for the recovery to boot normally (Thanks @m11kkaa)
Strip out unneeded files, so it will fit in the partition
TWRP 2.7.0.0 V1.0
Initial build
touch doesn't work until screen has turned off then back on
Do not flash! Only boot it
Support:
Live support is available via #MotoE on Freenode with your IRC client, or just click this link.
cybojenix said:
TWRP 2.7.0.0 V1.0
Initial build
touch doesn't work until screen has turned off then back on
Click to expand...
Click to collapse
Yay! We have a custor recovery! Thanks cybojenix, will try and report back ASAP. Now all we need is the kernel source, go Moto!
Yeaah!! Cheers!! Hope all bugs get fixed soon!!
And thanks for device tree too!!
OK guys, you're good for flashing twrp now. find any issues, don't be shy and pop up on here or freenode channel #MotoE
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Same as other Moto devices
startracker said:
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
startracker said:
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Evander_F said:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Click to expand...
Click to collapse
Added the link to the main thread. danke for the reminder
New build up, fixes external SDcard
cybojenix said:
Added the link to the main thread. danke for the reminder
Click to expand...
Click to collapse
And Thank you for the recovery ...v.1.1 installed successfully.
cybojenix said:
So here it is, TWRP for the Moto E
Click to expand...
Click to collapse
So it should work once I Suspend the device using power button?
Or do I have to wait till the black screen?
deej_roamer said:
So it should work once I Suspend the device using power button?
Or do I have to wait till the black screen?
Click to expand...
Click to collapse
you need to wait till the black screen, then press the power button
cybojenix said:
Touch won't work until after the device has suspended. I'll patch this once kernel source is up.
Click to expand...
Click to collapse
You might want to ask some of the Moto G developers about how they fixed touch for that device, since I remember a similar issue for quite a while with TWRP on Moto G
jonovw said:
You might want to ask some of the Moto G developers about how they fixed touch for that device, since I remember a similar issue for quite a while with TWRP on Moto G
Click to expand...
Click to collapse
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
cybojenix said:
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
Click to expand...
Click to collapse
This supports selinux kernal right?
Sent from my XT1022 using XDA Free mobile app
startracker said:
This supports selinux kernal right?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
yes
I am an idiot. D:
Edit: For those who didn't read OP like I did. Touch doesn't work until the screen times out for now.
cybojenix said:
So here it is, TWRP for the Moto E
Device tree added here
Download Here
Click to expand...
Click to collapse
Hello
Is there any chance you can create a version that would probably work in a non Moto E phone but shares most of the internals (ie MSM8610, Adreno302, etc).?
I've tried to boot it on a MSM8610 non-Moto E phone bit am getting the "Fastboot boot image : dtb not found" error.
kenshinta said:
Hello
Is there any chance you can create a version that would probably work in a non Moto E phone but shares most of the internals (ie MSM8610, Adreno302, etc).?
I've tried to boot it on a MSM8610 non-Moto E phone bit am getting the "Fastboot boot image : dtb not found" error.
Click to expand...
Click to collapse
Which device? There are two ways to do a dtb. Appended, or as a separate image.
You can get the stock dt image using unpackbootimg. If there isn't one there, it's appended to the zImage, in which case just remove the stuff about dt in BoardConfig
Sent from my Nexus 7 using Tapatalk
cybojenix said:
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
Click to expand...
Click to collapse
Hi,
I thought that this post might help you - http://forum.xda-developers.com/showpost.php?p=49122115&postcount=129
I'm building TWRP for Xperia T2 Ultra and am experiencing the exactly same touch screen problem. Although enabling the TW_IGNORE_MAJOR_AXIS_0 in the BoardConfig didn't work for me, it might just fix the problem for you I guess
Regards,
abcdjdj
TWRP Recovery
This thread, and all current work were @Eliminater74's. He has moved on, so I am going to pick up where he left off. He will be missed in the LG community.
Downloads:
H872
US997
H870
TWRP Version: 3.2.3-1:
Updated:
Replaced compressed kernel, so boot times are much lower.
Verified not working:
Clock
Verified Working,
Flashing ZIP/IMAGES
Needs Testing:
encryption
Wipe LG Lockscreen
kdzwriter (imported: said to possibly work for g6 and v30)
I am sure many more things.. Just give me time to work on it all..
XDA:DevDB Information
[RECOVERY] [TWRP - V3.2.3-1 For H870, H872, US997] [unofficial], ROM for the LG G6
Contributors
runningnak3d, Eliminater74
Source Code: https://github.com/runningnak3d/android_bootable_recovery
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Current Beta Version: 3.2.3-1
Created 2019-02-13
Last Updated 2019-02-13
Note: You must flash the 'IMG' File to install recovery, then reboot into recovery.
I want to give a huge thanks to: @zefie for much code and custom changes he made to TWRP that allowed me to use:
@zefie, Since much of your code was a huge mess, I picked out only a few things, Like the LG lockscreen wipe.........
Most of the rest I used Omni's gerrit and added in things..
as for device tree, I used yours as a ref, then updated to see what fits.. I managed to get TIME to work on AOSP/LOS not sure how well on stock..
but im next to sure it will.......
I added kdzwriter for peepz that wanna flash parts of kdz file to device.. but even know I was told that it should work for the G6 and V30, it still gives me a error on the kdz files when it test to see if its
compatible with device, which it is.. guess from looking at the code it analyzes your current GPT on your device and matches it to the one in KDZ, if no match it wont allow you to write anything..
so I emailed author and waiting to see if I get a response back one day..........
reserved #2
1st haha
---------- Post added at 03:29 AM ---------- Previous post was at 03:27 AM ----------
What's the kdz writer do?
jimbomodder said:
1st haha
---------- Post added at 03:29 AM ---------- Previous post was at 03:27 AM ----------
What's the kdz writer do?
Click to expand...
Click to collapse
plug her in or drop to a terminal and type kdzwriter
it will give you clear instructions........
I think it needs updating to allow for G6 and v30, and I already emailed the author on that............
Eliminater74 said:
plug her in or drop to a terminal and type kdzwriter
it will give you clear instructions........
I think it needs updating to allow for G6 and v30, and I already emailed the author on that............
Click to expand...
Click to collapse
Ah ok and yeah takes ages to boot up haha
Sent from my [device_name] using XDA-Developers Legacy app
h872, work!!! :good:
on older twrp can't mount /data in stok oreo rom
this version work perfectly for me
jimbomodder said:
Ah ok and yeah takes ages to boot up haha
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
when I re compile my kernels, I will remove that compile for size setting. cause that is why it takes so long to boot...... its gota de compress the kernel image...
Eliminater74 said:
when I re compile my kernels, I will remove that compile for size setting. cause that is why it takes so long to boot...... its gota de compress the kernel image...
Click to expand...
Click to collapse
Good good, it makes you think it's failed haha
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:11 PM ---------- Previous post was at 12:38 PM ----------
Also noticed vendor partition no longer shows up in mount settings
Sent from my [device_name] using XDA-Developers Legacy app
jimbomodder said:
Good good, it makes you think it's failed haha
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:11 PM ---------- Previous post was at 12:38 PM ----------
Also noticed vendor partition no longer shows up in mount settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
There is no vendor partition yet, at least not with my AEX ROM and device tree that I use...
the only vendor is system/vendor and /vendor that symlinks to system/vendor .................
vendor partition is for Treble devices which we are not yet setup for......
I was going to convert my G6 to Treble and allow for vendor partition which is like 500+ megs.. minus the same amount from system.........
But till that project is verified to work, I have yet to do it..........
Building another Update Recovery Package: Trying a few new things to see if I can get all to work like it should.
Vendor was added to backups for the ones that have 'VENDOR' partition, Its marked as removable so that peepz without it dont get errors:
misc is added to backup, so you dont lose your network mac stuff.....
data can also be backed up in whole with internal Storage added
laf partition can now also be backed up, Just in case peepz.................
At some point I will be removing the extra_sd partition section.. I see no need for it.. and its just a waste.. unless others can tell me otherwise..
it was only a good idea back when MultiROM was a thing.. Which today its not....... and no longer updated or maintained.......
So having that is not needed................
Great job @Eliminater74
I remember you from the G3. Glad to see you on the G6 as well.
TWRP Update:
V3.2.3 20180812:Grab in Downloads:
Changes: peepz that have a separate vendor partition can now back it up and mount it:
LAF partition is now backupable......
data now has a FULL Data Image backup, which also means internal storage:
Played with a few other things too, but nothing big.. I still need everything tested by others who are willing to take the plunge..
The above changes for the partition was only fstab flags changes to make that happen..... No biggie there......
I also added un official changes to twrp recovery it self,
meaning, They are on their gerrit, but not official merged yet..........
Check out my DevG6 github page under android_bootable_recovery repo for commit history I made and added.........
NOTICE:
I will fix the Mouse showing in next build, I removed the blacklist by mistake and that is why its showing.. as soon as I add the blacklist back
the mouse will be no more....... SORRY Peepz.............
Eliminater74 said:
@zefie, Since much of your code was a huge mess
Click to expand...
Click to collapse
So rude. But also so incredibly true. Haha.
Great work though. Obviously I haven't tried it since I can't, but just happy to see work still being done on it, and glad to be of some help.
Edit: That said, your way, which is probably more proper, is a mess to me. I couldn't find the fstab, so apologies if you already know this, but I also dabbled with /vendor support. Make sure you set it as removable otherwise users who do not have /vendor will get an error when backing up (even if they uncheck vendor, at least when I tried it).
zefie said:
So rude. But also so incredibly true. Haha.
Great work though. Obviously I haven't tried it since I can't, but just happy to see work still being done on it, and glad to be of some help.
Edit: That said, your way, which is probably more proper, is a mess to me. I couldn't find the fstab, so apologies if you already know this, but I also dabbled with /vendor support. Make sure you set it as removable otherwise users who do not have /vendor will get an error when backing up (even if they uncheck vendor, at least when I tried it).
Click to expand...
Click to collapse
sorry man, Didnt mean it to sound rude, you do great work.. and everyone has their own way to do things, as im so used to doing steps by steps because I have to reuse alot of things on my projects and need everything to be separated from other things.. But in all. your work is great............
and yeah, I used your fstab and just made some changes and its marked as removable.. I seen your comment on that in the fstab.. I do like that you left many comments for people to understand your work.
I am not building a test AEX Rom with the vendor create script added.. so ill see how that pans out............
thanks again for your help and work........
Eliminater74 said:
sorry man, Didnt mean it to sound rude
Click to expand...
Click to collapse
I was just kidding (if you think that code is a mess you should see my older code that even I have a hard time understanding. That is where the commenting came from haha)
@zefie,
Question, How are your coding skills on twrp? Mine are not that great and I dont understand the recovery stuff as much as it seems you do,
Here is the thing, a script was made that will create a vendor partition for you. what this script does is checks to see if you have one first..
if not then it checks to see if your system in correct size, then it creates the vendor partition and resizes the system..........
and yes it can be reversed,
the script was designed for twrp originally then LOS added to lge_msm8996-common device tree, but will only work on LOS, that once you install ROM it runs that script and checks everything..
I took that script as well as the Android.mk mods that allow for building the needed tools for the script to run in twrp........
I need an option made that will have a checkbox when you install a ROM, that lets you put a check int the box to pre run the script before installing the rom...........
that way.. people can convert their devices from twrp........
the script and needed tools are already added to the TWRP, not in current one I released yesterday.. but in the one I havent released yet...
so it can be ran manually.. I had to make alot of mods to get it to build the tools and all with twrp..
biggest tool needed was sgdisk............
but if you could help me out with the coding of that option for pre installs of rom.. that would be great........
btw again, that script checks if you already have the partition and if you do, it aborts the rest of the script and goes on to installing rom..........
Let me know if you can help me out here... thanks ..
good job.
surport the project treble？
Eliminater74 said:
WOW !!!
Backing up LAF/Download partition is the first for me on any TWRP for any devices :good:
Great job. Thanks for your hard work.
Click to expand...
Click to collapse