[xt10xx][CWM Advanced Edition] PhilZ Touch - Moto X Android Development

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Here is a note from the original thread's developer about what's coming or happening with this recovery and it's former relationship to CM11:
Originally Posted by Phil3759 View Post
To all developers:
Later versions should be stable but need a deeper debugging maybe
If you spread them, please mention to users it is work in progress
I also appreciate all reports and debug about new versions
It is a huge work I started: moving to AOSP and completely break with CWM
CWM is now poorly supported. I do not want anymore to be relying on average developers pushing random commits at their taste
So, it is better to break and live with an own project
Compatibility: I will try to maintain it with TWRP and CM new recovery at some time
CWM: if a developer decides to revive it will just follow probably. So, we don't really care
I will be monitoring it and try to keep compatibility if it ever has a future
Click to expand...
Click to collapse
Note from the contributor trying to help keep things up to date (Hachamacha, so you know who to blame):
I've switched to the new and not really debugged GHOST unified build because msm8960dt is no longer in the tree, should cover the Maxx and Ultra and Mini as well. Until then, try these builds if you like. Remember you can always revert to a working image over on goo.im if you need to either by flashing it from the recovery, or by using the .img file provided below, and flashing from either fastboot or flashify.
Just added the 6.58.7 build which is working for me but since it's new you'll need to leave debug logs if needed (see main thread) and has a number of enhancements: You can download from the usual spot in either .img or .zip format. Actually I'm not sure if that's true because the usual spot probably won't be named msm8960dt, rather "ghost" any longer. Just check out my recent (today) post in the main thread and see what the upshot was.
Click to expand...
Click to collapse
Latest unified GHOST version for the xt10xx's: 6.58.7 -
Click to expand...
Click to collapse
Changelogs:
6.58.7
- Source updates and fixes
Click to expand...
Click to collapse
6.58.4
- Fixes building errors and issues related to new CyanogenMod changes
Click to expand...
Click to collapse
Latest unified GHOST version for the xt10xx's: 6.57.9 -
[/QUOTE]
6.57.9
- fix install in "Free Browse Mode" from non vold managed volumes
Click to expand...
Click to collapse
Update v6.57.8 / CWM 6.0.5.1 / libtouch_gui 1.41
- fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
- merge CWM updates to selinux permissions for init services
- fix adb for 3.10 kernel
Click to expand...
Click to collapse
6.57.5 ::
- Update SuperSU
- merge a few SR/CWM changes and bug fixes
- fix aroma file manager issue with some slow mount/unmount devices
Click to expand...
Click to collapse
6.56.2
-
Click to expand...
Click to collapse
6.55.0
-add option to disable md5 from edify restore_rom command line
- this fixes restore of custom roms
Click to expand...
Click to collapse
6.54.9 - libtouch_gui 1.40
- support faster transfers through USB storage for voldmanaged devices
- fix compiling for devices with custom recovery key or ui files
--This version adds many enhancements in the code to better support storage volumes
--USB mount should have now good transfer speeds for vold volumes if you add needed entries in extra.fstab
Click to expand...
Click to collapse
6.50.6
- fix potential failure for TWRP backups (cause scan_mouned_volumes() not called)
- loki_recovery code clean up
- fix potential failure to reboot when checking config file
- never confirm wipe in ors scripts
- always show text in sideload mode
- support wipe_cache and clear_display edify script commands
Click to expand...
Click to collapse
6.48.4
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- libtouch_gui 1.30
Click to expand...
Click to collapse
Notes regarding 6.41.6:
- 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
Click to expand...
Click to collapse
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
Latest download links for each device, first by image, second by zip (e.g. 6.4x.x : img link: URL : zip link: URL) :
Moto X unified (ghost)
- 6.58.7: Image : http://d-h.st/SuL : Zip : http://d-h.st/g7u
- 6.58.4: Image : http://d-h.st/NRs : Zip: http://d-h.st/YZq
- 6.57.9: Image : http://d-h.st/CZT : Zip: http://d-h.st/VpE
Moto X unified (msm_8960dt)
- 6.57.8: Image : http://d-h.st/7IFk Zip : http://d-h.st/PzH
- 6.57.5: Image : http://d-h.st/RlF Zip : http://d-h.st/P95
- 6.56.2: Image : http://d-h.st/qle Zip : http://d-h.st/wNJ
- 6.55.0: Image http://d-h.st/yJs : Zip : http://d-h.st/UlX
- 6.54.9: Image http://d-h.st/MLT : Zip : http://d-h.st/efL
- 6.50.6: Image http://d-h.st/DIn : Zip : http://d-h.st/Iiz
- 6.48.4: Image http://d-h.st/yKU : Zip : http://d-h.st/fcH
Motorola Moto X variants:
- VZW (xt1060) - 6.41.6: Image : http://d-h.st/uuQ : Zip : http://d-h.st/hCo
- GSM (xt1058) - 6.41.6: Image : http://d-h.st/AA4 : Zip: http://d-h.st/pg5
- TMO (xt1053) - 6.41.6: Image : http://d-h.st/W6h : Zip : http://d-h.st/4Gj
- US Cellular (xt1055) - 6.41.6: Image : http://d-h.st/bCT : Zip : http://d-h.st/zGV
- Sprint (xt1056) - 6.41.6: Image : http://d-h.st/wkU : Zip : http://d-h.st/Pw6
- VZW (xt1060) - 6.41.5: Image : http://d-h.st/oc9 : Zip : http://d-h.st/N8X
- GSM (xt1058) - 6.41.5: Image : http://d-h.st/JCU : Zip: http://d-h.st/DQU
- TMO (xt1053) - 6.41.5: Image : http://d-h.st/Qxn : Zip : http://d-h.st/Vye
- US Cellular (xt1055) - 6.41.5: Image : http://d-h.st/Pwr : Zip : http://d-h.st/BBP
- Sprint (xt1056) - 6.41.5: Image : http://d-h.st/Zit : Zip : http://d-h.st/zmr
Click to expand...
Click to collapse
For the older builds (well, and the newer builds as they're propagated up to goo.im)
Download links
Last version can be found here:
Motorola Moto X variants:
- VZW (xt1060)
- GSM (xt1058)
- TMO (xt1053)
- US Cellular (xt1055)
- Sprint (xt1056)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Note: All credit goes to Phil3759 and the makers of CM11.
XDA:DevDB Information
[xt10xx][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Moto X
Contributors
Phil3759, hachamacha
Version Information
Status: Stable
Created 2014-05-06
Last Updated 2014-10-26

OMG! Thank you Philz! I've been using your recoveries on my previous phones (Galaxy S2, Note, S4, etc) and that's the only thing I was missing from Moto X. Now it is complete
Enviado de meu XT1058 usando Tapatalk

Any chance for the xt1056?
Sent from my XT1056 using XDA Premium 4 mobile app

VerneVerne said:
Any chance for the xt1056?
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you can flash any of these.

Yes, I was hoping your recovery would make it here. Thank you!
Sent from my XT1060 using Tapatalk

Phil3759 said:
I think you can flash any of these.
Click to expand...
Click to collapse
I tried the xt1060 on my sprint variant with no luck
Sent from my XT1056 using XDA Premium 4 mobile app

VerneVerne said:
I tried the xt1060 on my sprint variant with no luck
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Provide a link to a github device tree on kk/cm11

Rogers 1058 support? I guess if it works or not on at&t may answer that.
Regardless of the answer....thanks for your work.
Sent from my XT1058 using Tapatalk

XT1055 would be awesome too man. US Cellular.
Sent from my XT1055 using Tapatalk

Brilliant!!! Thank You!!!
Works great on the Droid Maxx DE!

Compatible with KK?
EDIT: Works like a charm in my XT1058 with KitKat!
Great job, man!

This is so nice, I had no idea Philz Touch for my N7 '13 was so slow switching between screens until I noticed how blazing fast it is on my Moto X, haha. Now I understand what they were saying on the N7 forums.
Sent from my XT1060 using Tapatalk

Failed to download.
Sent from my XT1053 using xda app-developers app

kenosis said:
Failed to download.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
Goo.im can act up every now and then, downloaded fine for me. Keep trying?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Excellent work! Thanks a lot! Especially for OTG support in recovery!
EDIT: Just made backup and restore from nandroid using OTG (external SD card) - phone works as expected!

Any chance of having a mirror of the downloads?
I have an xt1058 and goo.im gets blocked on my work firewall

Update 6.09.8
- US Cellular (xt1055)
- Sprint (xt1056)
Refresh goo.im in a while

Not seeing the download link for xt1056 on the page.

I believe he said he needs to refresh it first.^^
Sent from my XT1055 using Tapatalk

Phil3759 said:
Update 6.09.8
- US Cellular (xt1055)
- Sprint (xt1056)
Refresh goo.im in a while
Click to expand...
Click to collapse
Anything of note between 6.09.6 you released yesterday for vzw/tmo...?

Related

[TOOLKIT PC+MAC] Nx4Toolkit v1.2

Nx4Toolkit (PC&MAC)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features :
-Unlock Bootloader /work
-Root /work
-Installing Custom Recovery /work
-Get back to stock /work but you may have to make a factory reset in the recovery menu
-Install a custom ROM
-Enable OTG
-All in one function : Root+CWM+Unlock bootloader /need testers
-Install kernel /work
-Backup-Restore /work
-Restart Fastboot-Recovery /work
-Check for updates
Click to expand...
Click to collapse
Please install the drivers before using, they are not included.
The toolkit works only with android 4.2.2, you shouldn’t test it on 4.2.1 or lower. This toolkit is based on adb and fastboot tools.
To use the toolkit, you may have to put your device in USB debugging mode. To enable it, go to settings / about phone and press quickly the build number
DOWNLOAD HERE FOR PC (1.2.0-F >300Mo)
You have to install the toolkit in the root directory of your hard drive or in directory where you have read-write rights (like desktop).
****************************************************************************************​
Nx4Toolkit 1.2 MAC​
Features :
-Unlock Bootloader
-Root
-Install custom recovery (cwm / twrp)
-Restore your device as its stock state
-All in one function : Root+CWM+Unlock bootloader
-Install a custom ROM (such as CM or PA)
-Install kernel
-ENABLE OTG
-Backup-Restore
-Restart Fastboot-Recovery
Click to expand...
Click to collapse
You don't need any driver for the Mac version. The program is a .pkg (installer). You don't need to be admin of your computer to install or run the toolkit. But, you have to install the program on the system drive.
The program is installed in ./nx4toolkit (./ means home). To run it just click on the icon on your desktop ( the icon is included in the .pkg).
Works with OSX 10.5 and higher.
DOWNLOAD HERE FOR MAC (1.2.5-L <50MO)
DOWNLOAD HERE FOR MAC (1.2.5-F >300Mo
****************************************************************************************​
Nx4Toolkit GRAPHIC 1.35 MAC​
​Features :
-Unlock-lock Bootloader
-Root
-Install custom recovery (cwm / twrp)
-All in one function
-Backup-Restore
-Restart Fastboot-Recovery
Click to expand...
Click to collapse
You don't need any driver for the Mac version. The program is a .zip : Extract and copy it to your /Application folder
Tested with OSX 10.7 and 10.8
DOWNLOAD HERE (1.35 <50MO)
Now available on the HackStore : search for Nx4Toolkit :good:
Thanks to : Chainfire (SuperSu), Efrant (Back to stock tutorial), Franciscofranco (FrancoKernel), Koush & CWM team (CWM).
I’m not responsible in case of bricked devices
Help
Why a L and a F version ?
L means lite : the two versions offers the same functionnalities but the F (full) version include the system images of android. If you just want to root your device, you can choose the L version. If your device has some problems (android won't boot...) use the Full version to restore it.
The L version is about 50Mo, the F one is about 350Mo.
I don't really know Android, should I use this toolkit ?
You use this toolkit at your own risks. I'm not responsible in case of bricked devices. If your device has some problems, search a tutorial explaining how to restore your device by flashing things with Adb & fastboot : Efrant has made a really easy to understand one.
Your toolkit don't work, what can I do ?
Report your problem here, if there's something wrong with the toolkit : I'll fix it.
Re: [TOOLKIT] Nx4Toolkit v1.0
What does this toolkit do that others don't?
[LG NEXUS⁴] [LIQUIDSMOOTH] [MATR1X] [POETIC BLK BUMPER] [APEX PRO] [TAPATALK PRO]
dEris said:
What does this toolkit do that others don't?
[LG NEXUS⁴] [LIQUIDSMOOTH] [MATR1X] [POETIC BLK BUMPER] [APEX PRO] [TAPATALK PRO]
Click to expand...
Click to collapse
I think it's just an alternative. Choices are good. :victory:
scream4cheese said:
I think it's just an alternative.
Click to expand...
Click to collapse
Yes, that's it.
The toolkit don't really offers new functionalities, excepted the native custom Kernel installation. But i'm planning on others options to make the toolkit more efficient :good:
Re: [TOOLKIT] Nx4Toolkit v1.0
Bzh2610 said:
Yes, that's it.
The toolkit don't really offers new functionalities, excepted the native custom Kernel installation. But i'm planning on others options to make the toolkit more efficient :good:
Click to expand...
Click to collapse
I love more options! thank you very much!
Sent from my Nexus 4 using Tapatalk 2
I've just uploaded the 1.0.1, it offers more options to the user :
-Possibility to boot kernel and recovery
-TWRP is now included
-Insecure boot image and stock kernel are now available.
-Possibility to flash the stock recovery without wiping everything.
Hope you'll enjoy it !
The original link has been updated
Re: [TOOLKIT] Nx4Toolkit v1.0
I've added the Mac version with a feature to enable USB OTG (Thanks Ziddey !)
Have fun !
Sent from my Nexus 4 using xda app-developers app
I think the nexus 4 toolkit which is stickied stopped working properly after the 4.2.2 update when it comes to rooting etc... Most things still did tho... So if this works all around then that's good...!
Keep it up...
Sent from my Nexus⁴
1.2 Mac update
Just a post to tell you that I've updated the Mac toolkit.
New things :
-Toolkit update function
-OTG install fix
-Get back to stock with Android 4.2.2
-The possibility to install a custom ROM from the toolkit (such as P.A or CM)
I think it's one of the last update before Android 5.0, the P.C version will be up to date this week to have the same functions as the Mac version
Important note : The new version is very big (about 330Mo) cause of the android system.img included. I think you would like a lite version of the program including only the toolkit essentials : i'm planing on it.
Here gave error in time to start the toolkit. The system can not start the program, because the original item could not be found.
I'm using ML 10.8.3
mariojuniorjp said:
Here gave error in time to start the toolkit. The system can not start the program, because the original item could not be found.
I'm using ML 10.8.3
Click to expand...
Click to collapse
Oh ! I know the reason of this problem : the file on the desktop is pointing of a file located on my personal home directory. I'm actually fixing it.
If you want to use the toolkit right now, just go to Macintosh hd / User / Your user name / Nx4toolkit / Nx4toolkit
thanks for reporting.
Bzh2610 said:
Oh ! I know the reason of this problem : the file on the desktop is pointing of a file located on my personal home directory. I'm actually fixing it.
If you want to use the toolkit right now, just go to Macintosh hd / User / Your user name / Nx4toolkit / Nx4toolkit
thanks for reporting.
Click to expand...
Click to collapse
Thanks man!
Fixed
To fix the problem : type "ln -s ~/Nx4toolkit/nx4toolkit ~/Desktop/Nx4toolkit-1.2" without quotes in terminal.app
The fixed full package is actually uploading. I'll edit the O.P tonight.
Edit : the original package is now fixed
1.2 update
I've updated the windows version to 1.2
Now, you can enable OTG, install a custom ROM, restore your device as stock without downloading files, check for updates directly from the toolkit.
The backup and restore are a little bit different, you can give a name to the backup files and restore any ".ab" file to your device.
Hope you'll enjoy this update. If you have any problem, please, report it to this theard. Thanks.
Bzh2610 said:
I've updated the windows version to 1.2
Now, you can enable OTG, install a custom ROM, restore your device as stock without downloading files, check for updates directly from the toolkit.
The backup and restore are a little bit different, you can give a name to the backup files and restore any ".ab" file to your device.
Hope you'll enjoy this update. If you have any problem, please, report it to this theard. Thanks.
Click to expand...
Click to collapse
Thanks for this piece of software, needed something like this for the mac to backup my Nexus 4.
Any ETA on 1.2 mac update? Also does the USB OTG work with a standard OTG cable or is a special cable needed for the extra power?
randomvector said:
Thanks for this piece of software, needed something like this for the mac to backup my Nexus 4.
Any ETA on 1.2 mac update? Also does the USB OTG work with a standard OTG cable or is a special cable needed for the extra power?
Click to expand...
Click to collapse
Now you can fully backup your nexus 4 on your mac !
I've made two versions of Nx4Toolkit : a lite (just the essentials) and a full one including the android images.
For the OTG, it's based on Ziddey work, so you'll need to see his own theard on it for a support, but I'm sure that an external power is needed.
****
Would you like an user interface for Nx4Toolkit ?
I wish to uninstall the full version for the lite, is it just a matter of dragging the folder to trash and deleting or is there a cleaner way?
There's no "clean way" to uninstall. Just delete the Nx4toolkit folder in your home directory. But I think you can start the new install without deleting nothing : It will overwrite the actual Nx4Toolkit.
Sent from my Nexus 4 using xda app-developers app
Bzh2610 said:
Now you can fully backup your nexus 4 on your mac !
I've made two versions of Nx4Toolkit : a lite (just the essentials) and a full one including the android images.
For the OTG, it's based on Ziddey work, so you'll need to see his own theard on it for a support, but I'm sure that an external power is needed.
****
Would you like an user interface for Nx4Toolkit ?
Click to expand...
Click to collapse
Great job man! = D
Tell me something: When I want to spend the stock image, just put the. Tgz image in some folder there, and the toolkit will already recognize and restore or it will download from Google's servers?

[DEV][RECOVERY] TWRP 2.6.3.1 for Moto X - UNLOCKED BOOTLOADERS ONLY ! -

What is TWRP?
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelogs
[RECOVERY][OFFICIAL] TWRP 2.6.0.0 touch recovery [2013-07-23]
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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:
Tablet look:
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Click to expand...
Click to collapse
I don't have this device but I build this for this great community.
Test and report.
Also,if something doesn't work,give me a recovery log.
Downloads :
Test Build #1 - http://d-h.st/Wne
Test Build #2 - http://d-h.st/Nhf
Test Build #3 - http://d-h.st/EGP
Click to expand...
Click to collapse
Source code : https://github.com/oblikas/android_device_motorola_ghost
Credits:
@mattlgroff for his device tree
Good luck :good:
mattlgroff said:
Good luck :good:
Click to expand...
Click to collapse
Thanks mate
Can you give it a shot?
oblikas said:
Thanks mate
Can you give it a shot?
Click to expand...
Click to collapse
I would if I had a Moto X to try it out on. :fingers-crossed:
mattlgroff said:
I would if I had a Moto X to try it out on. :fingers-crossed:
Click to expand...
Click to collapse
Oh sorry,I didn't know lol
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
hidea said:
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Nice,thanks
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
flashallthetime said:
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
Click to expand...
Click to collapse
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
oblikas said:
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Also insert your data cable in your device and see how is it recognized in device manager.
Sent from my Nexus 4 using xda app-developers app
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Oops,my mistake
Sent from my Nexus 4 using xda app-developers app
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
mattlgroff said:
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
Click to expand...
Click to collapse
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Works fine for my TWRP test?
http://batakang.com/ftp/recovery/ghost/twrp_test_touch69.img
Sent from my SGH-M919 using Tapatalk 2
New test build
Link : https://d-h.st/OZm
oblikas said:
New test build
Link : https://d-h.st/OZm
Click to expand...
Click to collapse
Give it a try again, cross my fingers and toes
Sent from my XT1058 using XDA Premium 4 mobile app

★★★[RECOVERY] Latest TWRP 2.7.0.0 touch recovery★★★

★★★[RECOVERY] Latest TWRP 2.7.0.0 touch recovery★★★
Note : This TWRP is no longer Supported Use the Stable TWRP posted here
★★★Team Win Recovery project TWRP 2.7.0.0 Port for Canvas HD[19 March 2014]★★★​
It took me nearly 20 hrs to figure out the problems occured while porting ..Hit Thanks if you really like my Work..It encourages me to do some more stuffs like this
About TWRP:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Screenshot(v2.5.0.0):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: Latest TWRP 2.7.0.0 for Micromax Canvas HD
Download TWRP 2.6.3.0
Sources : http://yadi.sk/d/fmIOi_ee6ADpi
Instructions for flashing in your phone:
1.Download the recovery and Put it in root of your SDCARD
2.Open Mobile uncle tools and select Recovery Update
3.Flash recovery file
4.Done
Bugs/Disabled:
1.Auto root,ADB and symbols keyboard from TWRP disabled to reduce recovery size
2.If u find any bugs..Bring it to my notice​
Instructions for flashing using SP Flash Tools:
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with twrp recovery.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt
5.Check only recovery.img, preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware
> Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11.Disconnect your phone.
Disclaimer: By Downloading and flashing the Recovery may void your Warranty ..Ill not be Responsible For any harm .Do it on your own Risk
Credits:​Dees_Troy For base Recovery
@michfood For his Repacking Tools
@yuweng For his base recovery and help
@tEaM Win Recovery Project
@myself for porting
Changelog Of TWRP
Updatelog:
19-3-2014- Updated TWRP V2.7.0.0
6-12-2013- Fixed USB Storage Mount Option
1-12-2013- Fixed Compression Backup option
23-11-2013- Released TWRP v2.6.3.0
Changelog Of TWRP:
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
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Looks nice. could you please port same to C4? I'm dying for one
Waiting for it!!! Can I just flash it using mobile uncle tools??
Sent from my S39h using xda app-developers app
Please make a zip file for all those who are already rooted
Many thanks!! you did it...
Wow gonna try it for sure....
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
I knew that our loving Dev @suhas.holla will cooking something...:good::good:
Flashed using MobileUncle & flashed Fonts from Ex-Sd Card... Till now looking Perfect..
Tnks for New Recovery Bro...
Expecting more from u always....
:victory::good::fingers-crossed:
Looks cool bro keep it up..I wanna flash now
Sent from my Micromax A116 using Tapatalk
Bro, recovery always comes with .img format which is to be restored to the "Recovery" partition.
vismaiy said:
Waiting for it!!! Can I just flash it using mobile uncle tools??
Sent from my S39h using xda app-developers app
Click to expand...
Click to collapse
Yes... You can Flash it through mobile uncle tools
It seems it's missing nvram partition backup....
Sent from my S39h using xda app-developers app
suhas.holla said:
Instructions for flashing using SP Flash Tools:
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with cwm twrp recovery.
.........................................
Click to expand...
Click to collapse
. that apart, good job, buddy!
---------- Post added at 10:56 PM ---------- Previous post was at 10:56 PM ----------
deeplyyoung said:
.....Flashed using MobileUncle & flashed Fonts from Ex-Sd Card... Till now looking Perfect.....
Click to expand...
Click to collapse
look again. new file uploaded 2013-11-23 10:30:29.
m0han said:
. that apart, good job, buddy!
---------- Post added at 10:56 PM ---------- Previous post was at 10:56 PM ----------
look again. new file uploaded 2013-11-23 10:30:29.
Click to expand...
Click to collapse
Code:
[COLOR="red"]Size: (6248448 bytes)
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2[/COLOR]
Edit: MD5 Sum is same
deeplyyoung said:
previous one
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2
new one
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2
Click to expand...
Click to collapse
same md5?!!!!! so, have you flashed the new one too?
m0han said:
same md5?!!!!! so, have you flashed the new one too?
Click to expand...
Click to collapse
Just Chked & sorry both r same files have mentioned wrong Sz.
vismaiy said:
It seems it's missing nvram partition backup....
Sent from my S39h using xda app-developers app
Click to expand...
Click to collapse
Just uploaded the new recovery with NVRAM backup option...Download the new TWRP file and flash it
U will get nvram backup option
suhas.holla said:
Just uploaded the new recovery with NVRAM backup option...Download the new TWRP file and flash it
U will get nvram backup option
Click to expand...
Click to collapse
M on it
Edit: Flashed & found nvram partition backup...tnks
Well I downloaded the new one but I still can't find it...
Sent from my S39h using xda app-developers app
withou auto root
Twrp without auto root that was the feature that i liked most in twrp and will the old version work correctly on flashing any kind of roms?
Currently i m on TWRP 2.5
@suhas.holla Bro today have tried to take Backup using TWRP 2.6.3.0 but getting error:-
pls look into this & solve it...
Code:
[COLOR="Red"][BACKUP STARTED]
*Backup folder: /sdcard/TWRP/BACKUPS/Micromax_A116/2013-11-24--11-03-31....
E:Unable to create folder: /sdcard/TWRP/BACKUPS/Micromax_A116/2013-11-24--11-03-31....
E: Failed to make backup folder.[/COLOR]

[ROM][3/13/2014][AT&T X+ S5 eXtreme V1.0.3.4]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[U][COLOR="Red"][B][SIZE="4"]S5 eXtreme V1.0.3.4 [/SIZE][/B][/COLOR][/U] - [COLOR="Red"]Release Date - 3/13/2014[/COLOR]
New boot.img included and required
Updated Firewall scripts
Fixed crashing google text to speech
removed more hotspot restrictions
added secondary app install script (first boot only)
[U][COLOR="Red"][B][SIZE="4"]S5 eXtreme V1.0.3.3 proposed updates[/SIZE][/B][/COLOR][/U] - [COLOR="Red"]Release Date - 2/18/2014[/COLOR]
[B][I][COLOR="Green"]New boot.img included & required[/COLOR][/I][/B]
1. iptables rules for added security (userinit.d)
2. iptables rules for HotSpot masquerade (userinit.d)
3. improved logging to new sysinit structure
4. improved logic in sql optimization scripts
5. added memory management and cache cleaning capabilities to init scripts
6. updated all apps
7. new default background
8. new boot animation
[B][U][COLOR="Green"]In Development[/COLOR][/U][/B]
1. custom compiled busybox for enhanced init.d support
[B][U]V1.0.3.2[/U][/B] - [COLOR="Red"]Release Date: 01/30/2014[/COLOR]
[B][COLOR="Red"]New Boot image required[/COLOR][/B]
Fully working 100%
HTC Dialer FC's fixed (replaced contactsprovider.apk)
All google apps working and updated (yes including Play Store)
On-Demand governor tweaks + lowmemory tweaks
all sqlite3 DB's checked and vacuumed on boot
All new completely re-written init.d support including userinit.d support by default
Native WiFi Hotspot patch included as optional during flash.
APN's updated
xPosed Mods updated
[B][U]RC2[/U][/B] - [COLOR="Red"]Release Date: 01/11/2014[/COLOR]
[B]!!!First Boot can take up to 5 minutes, have patience[/B]
4G/LTE Data throttling removed
WiFi Hotspot throttling removed
Native WiFi Hotspot enabled
IpTables firewall enabled for better security
Minor changes to default configuration, including EQS Tiles
Improvements to boot.img (YES flash the new custom_boot.img)
[B][U]Beta 2 (Will be released as RC1) [COLOR="Green"]Release date 01/01/2014[/COLOR][/U][/B]
[B][U][COLOR="Red"]NOTE: First boot can take up to 5 minutes be patient[/COLOR][/U][/B]
Google Search FC
Facebook in blinkfeed now updates
sound image and configuration fixed
Capacitive button backlight (re-enabled)
Sweep Panorama (random FC's fixed)
Added Telus SP APN Settings
Removed all Read Only attributes from carrier WiFi AP's
sdcard performance (boot.img)
Launcher performance tweaks (services.jar edits)
File System performance enhancements
WiFi/Data performance enhancements
Battery life enhancements
Memory management
[B][U]Beta1[/U][/B]
Stable Release
Rebuilt from 2.15.502.1 system dump
DO NOT UPDATE HBOOT
rebuilt from scratch with latest SDK and Tools
Rebuilt under linux 64bit development environment
Unsecured boot image
Unlocked APN Settings
init.d support added
Unlocked services.jar
Updated hosts file
WiFi fixed and tested
Bluetooth fixed and tested
GPS Fixed and tested with average 2s first fix time
xPosed framework installer included (mods)
Sense5 Toolbox xPosed module included (mods)
Zipaligned with latest SDK Tools
All google apps and components updated
Code:
[B]Whats Working[/B]
4G lte
Mobile Data
WiFi
Native WiFi Hotspot
Bluetooth
GPS
All apps
Camera
SMS/MMS
Browser/Chrome
Widgets
[B]Not Working[/B]
You tell Me
[STRIKE]WiFi Hotspot - Use third party hotspot app (Recommended is the google wifi tether v3.3beta2 or 3.4 experimental)
Settings needed for hotspot may very depending on what version of the app is used.[/STRIKE]
[STRIKE]HTC Dialer (call button does not work)[/STRIKE]
[STRIKE]HTC Sync Manager (random FC)[/STRIKE]
[STRIKE]GPU Overclock issue (Runs at 520mhz causing heat issues during heavy loads)[/STRIKE]
New boot image required.​Extract boot.img from zip file and place in your sdk platform tools folder, (or wherever your adb tools are located)reboot device to bootloader and connect it to your PC.
From a command prompt type:
1. fastboot flash boot boot.img
2. fastboot erase cache
reboot to recovery and flash ROM.
Click to expand...
Click to collapse
#~NOTICE~#​Team Blackout is not responsible if you blow up your house, your dog eats your homework, the zombie apacolypse, your wife/husband divorcing you or if your device turns into an unrecognizable smoldering pile of plastic. by reading this you agree to take all responsibility for any damage you do to the universe, your device, your marriage or your failing grades in school or college.​
Click to expand...
Click to collapse
I am not including the hboot and I do not recomend you update it as of yet either as it will prevent you from reverting to previous ROM versions.​
Out of alpha and into Beta, xposed installer and sense5 toolbox included in mods install in aroma.​Please do not ask for RUU downloads and don't ask for updates it is likely this will not have any major changes until the RUU is made public. I will keep you posted as progress continues.​
Supports xPosed Framework Check it out HERE​
I recommend installing the Sense5 Toolbox module as it provides the most comprehensive set of tweaks available​
Click to expand...
Click to collapse
@sixcarnage - for the new OP screenshots
@Lloir - For providing the system dump
@WindyCityRockr - For alpha and beta testing
@911Jason - For beta testing HUGE thanks for all the hotspot testing
@scrosler - Over at the LG G2 forums, he is the original author of the ATT Tether hack used here.
Please remember to use the Q&A thread for questions, keep this thread for development related topics​
XDA:DevDB Information
Blackout_eXtreme_Sense5, a ROM for the HTC One X+
Contributors
cstayton
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
ROM Firmware Required: hboot 1.40 and up
Version Information
Status: No Longer Updated
Current Stable Version: 1.0.3.4
Stable Release Date: 2014-02-18
Created 2013-12-12
Last Updated 2014-04-11
Mirrors
​
Wallpapers, Themes and Patches
Blackout Wallpapers app
Save the attachment to your sdcard and install from there
Make sure you have unknown sources enabled
Native WiFi Hotspot Patch
Available in downloads Tab or from WiFi Hotspot Fix
confirmed working by tester
HUGE THANKS to @scrosler over in the LG G2 forums his thread is HERE
Please visit his thread and thank him for his work, he is the original developer behind this fix i just rewrote it for use on HTC devices.
Google Services Framework Fix (step by step instructions)​This will fix Play Store issues​MAKE A NAND BACKUP OF YOUR NON WORKING ROM​
Code:
STEP 1: Restore a working backup (one you know play store worked on)
STEP 2: Download a windows android file browser (I recommend Android Comander)
STEP 3: Connect your device to your PC, Open the android file browser
STEP 4: Browse to /data/data and locate "com.google.android.gsf"
STEP 5: Copy the folder from STEP 4 to your sdcard (remember this location)
STEP 6: Restore your non working ROM from in recovery, Reboot
STEP 7: using a root explorer (or the windows android browser) locate the folder from STEP 5
STEP 8: Copy the folder from STEP 5 into /data/data make sure you choose to overwrite the folder and files
STEP 9: Reboot (You must reboot first, do not immediately try to open play store)
STEP 10: Once rebooted test Play Store, Google Plus and Hangouts all should work fine.
I realize this seems like a daunting task just to fix the Play Store,
but there is no easier way at this point to accomplish this the Google account MUST exist before restoring this folder
in order for the fix to work.​
Click to expand...
Click to collapse
such a good idea not to give the hboot exe, this was the reason i never gave it out, except to devs nice job btw!
Lloir said:
such a good idea not to give the hboot exe, this was the reason i never gave it out, except to devs nice job btw!
Click to expand...
Click to collapse
Couldn't have done it with out your system dump :good:
Added some screenshots, (with xPosed framework installed)
If you need any extra help or testing, I have the leaked Hboot flashed and some basic ROM skills. :highfive:
WindyCityRockr said:
If you need any extra help or testing, I have the leaked Hboot flashed and some basic ROM skills. :highfive:
Click to expand...
Click to collapse
ill keep you in mind when i get a little further along, still some bugs with the xposed framework and coupl other things yet
I have an ATT ONE X+ I don't use that I could use to test anything.
Sent from my HTC One using xda app-developers app
m1ke420 said:
I have an ATT ONE X+ I don't use that I could use to test anything.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
alpha3 is in the devdb downloads have at it and enjoy
cstayton said:
alpha3 is in the devdb downloads have at it and enjoy
Click to expand...
Click to collapse
Please, the download and Q&A link. Thanks.
dttung80 said:
Please, the download and Q&A link. Thanks.
Click to expand...
Click to collapse
this is a devdb project, scroll to the bottom of the page and change your xda to the 2013 beta and then the download Q&A and bug report tabs will display along the top of the thread
cstayton said:
this is a devdb project, scroll to the bottom of the page and change your xda to the 2013 beta and then the download Q&A and bug report tabs will display along the top of the thread
Click to expand...
Click to collapse
Found, thanks a lot.
Waitting for your next release with wifi fixed.
Regards,
Sent from my HTC One X+ using XDA Premium 4 mobile app
No more builds until official RUU is released.
Sent from my HTC One X+ using xda app-developers app
Beta 1 now available
OK, OK, OK so sue me. I know I said no more builds till the RUU dropped but I couldnt resist.
Beta 1 is now available in Downloads​
Everything appears to be working great, though I am still on the new Hboot, so it's more likely to work fine. :silly: I'm running it with the stock kernel, but what are the benefits of an unsecured boot.img?
WindyCityRockr said:
Everything appears to be working great, though I am still on the new Hboot, so it's more likely to work fine. :silly: I'm running it with the stock kernel, but what are the benefits of an unsecured boot.img?
Click to expand...
Click to collapse
Insecure boot image lets you use adb remount, and adb push or adb pull etc. to /system and its contents.
also the included boot image has init.d support, sdcard performance tweaks and evitareul_common tweaks. so you will get better performance when streaming large video files or playing music from your /data/media folder
great but 1 bug
Flashed the rom and everything is working, except Google search. Every time I use voice search I get Google search has stopped. Super smooth though. Great work.
jbharbin said:
Flashed the rom and everything is working, except Google search. Every time I use voice search I get Google search has stopped. Super smooth though. Great work.
Click to expand...
Click to collapse
ok yes I can reproduce ill look into it. please post in the bug reports section the steps you used to reproduce and a short description of the problem, that way I can keep track of all of the reports of bugs in one spot.
Beta2 fixes
Work on Beta 2 continues below list explains the fixes and improvements
Fixed/Added
Google Search FC
Facebook in blinkfeed now updates
sound image and configuration fixed
Capacitive button backlight (re-enabled)
Sweep Panorama
sdcard performance (boot.img)
Launcher performance tweaks (services.jar edits)
File System performance enhancements
WiFi/Data performance enhancements
Battery life enhancements
Memory management
In Progress
HTC Dialer (call button does not work)
HTC Sync Manager (random FC)
GPU Overclock issue (Runs at 520mhz causing heat issues during heavy loads)
Nice list of fixes there, thanks for your work! I can't wait to give beta2 a try...

[SCRIPT] [tool] [windows] [4.4] convert any rom to full f2fs

This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)

Categories

Resources