Should be working fine but it's thoroughly untested so expect errors at some point.
It's for cyanogenmod installations where /custpack is mounted to /system/app, if there is a request i'll make a version that mounts /custpack to /custpack but for now this is it.
I take no responsibility for what this will do to your phone, it's entirely possible that it will kill your phone and even cause a rift in the space time continuum which will kill us all.
Anyway, here it is, flashable via fastboot as usual, if it goes to stable i'll make an installer for it to install via CWM.
For those not comfortable with flashing via fastboot or who don't have access to a computer at this time, use flash_image via terminal, it should work fine.
Latest version:
cwm_touch_cocktail_6.0.2.7-testing-V2.img
MD5: feb35010a527de42c6c68d6987b939e1
Old versions (kept but not recommended):
cwm_touch_cocktail_6.0.2.7-testing.img
MD5: da314f6eb6429bc3530539d8a0e9e20a
Changelog:
2013-01-09
* Fixed buttons, you can now scroll, select and go back using the buttons.
* Fixed backup, /custpack is now linked to /system/app, this should also make it compatible with older roms. (Remember, this is still testing)
* Added mountpoint for /sd-ext to fix nandroid backups for A2SD/S2E/Links2SD installed apps.
* Fixed some glitches and updated kernel code.
2013-01-08
* initial release
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Hylix said:
Just flashed it to my mobile and thus far it looks promising. Currently I am not planning to change my rom yet so I haven't confirmed if it is able to flash a rom I only saw it boot.
A little thing I noticed though.
When CWM boots and you are in the main menu the menu fills around 80% of the screen. But when you go to another menu lets say flash something from SDCard it only fills up 50% of the screen and you have to scroll a lot to reach the bottom.
Also the buttons are not working at all?
When you press some of the buttons it starts doing weird stuff..
It seems like the volume buttons and the power button work currectly but the buttons at the bottom of the screen are weird.
Click to expand...
Click to collapse
I had completely forgotten about the bottom buttons TBH, i'll fix that in a future version.
Regarding the screen space, it's not much i can do about that ATM but i'll keep it in mind when and if it gets to stable.
Awesome looking good so far
Really cool. Just point and I'll help test.
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Mrwargod said:
Downloading and testing.
With this we can backup and restore CM/PA/PAC roms right?
Click to expand...
Click to collapse
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
tumaini418 said:
Really cool. Just point and I'll help test.
Click to expand...
Click to collapse
Would be great it you have the opportunity.
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
master' said:
When i use key test section, its dont back main screen and i need unplug battery.
You did great job thanks a lot...
Click to expand...
Click to collapse
You are welcome.
Jinxxed said:
If you mount /system/app in mounts and storage it should work just fine.
I'm probably going to write a script and put it in the place of the nandroid/nanddump/nandwrite files so /system/app is mounted before the backup/restore is written.
Just added some stuff to it, partitioning sdcard and support for sd-ext (and swap).
Should work well with an init.d script and s2e for those interested in larger storage for apps.
(simple script to mount /dev/mmcblk1p2 to /sd-ext would work)
Click to expand...
Click to collapse
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Mrwargod said:
Yes, having that automated would be great. If i could backup/restore/install zip's all in one CWM that would be awssome and render it definitivelly daily usable. And way easyer for me to test more roms without the concern in loosing my previous rom.
Click to expand...
Click to collapse
Should work fine now, to check if it is, analyze the content of your /sdcard/clockworkmod folder.
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Mrwargod said:
Already on it to try the latest version of PAC.
I'll feed you on how it went.
---------- Post added at 11:39 AM ---------- Previous post was at 11:18 AM ----------
The link is dead Jinxxed, or is it still uploading?
Click to expand...
Click to collapse
I mistyped the link. :silly: It's fixed now.
Sorry about that.
Yeah, i had already figured out the correct link anyway.
Thanks, testing!
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Mrwargod said:
Wipe battery stats is missing in advanced menu.
Backup / Restore - Not working properly - Some of my apps got lost in restore, namedelly all the gapps, some launchers (holoHD), some file explorers (root file explorer), google account, . . .
Flash zip - ROM flashed ok but gapps didn't flashed, neither did an aditional mod.
But it's really looking really good. And the hardware buttons are fixed.
Keep up the good work.
Click to expand...
Click to collapse
Thank you.
It's a weird result since that means that the backup has problems with both /data and /system/app (i assume since google account and launchers not installed via CWM are stored on /data). It really should be all or nothing, one would think...
There is a problem with mounting /system/app for some reason, that's why gapps isn't installed properly, i'll look into it.
It should be easy enough to fix though, expect a new version within the next couple of days.
Will post the same post here as in Benetnath his PAC rom cause maybe it has something to do with CWM?
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Just ran against a problem with doing the PAC update.
All my gapps seem to be broken and some apps crash on start up.
I had the first PAC rom running and flashed the newest over it while clearing my cache (tried flashing the gapps after this but still didn't fix it)
After this I did a complete reset and flashed it and now it seems to work.
Don't know if its the ROM or if its the new touch CWM which is still in testing..
NOTE: It seems like other people succeeded in flashing the updated rom over the previous rom.
I am not the only one with this problem and it seems like there are other people who have the same problem with the other CWM so ignore this all
trying to flash image in terminal in phone. i keep getting "error scanning partitionsfailed with error: -1
??????????
anyone?
nevermind i went ahead and did it the way i know how.
2nd Edit: just did a backup and restore. Seems to have worked fine.
I couldn't mount usb though.
Great work man. Between you and Benetnath we should be cooking with gas soon.
Thanks jinxxed.
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.
was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.
The zip file seems to be corrupt. Could you re-upload plz
worked great on my end, no problems.
khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .
wow this method really blaze hellfire much thanks to your( you) & (rom dev)
Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.
dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .
thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid
dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA
Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium
It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.
[RECOVERY] [3/28/16] TWRP 3.0.0-1 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.x for the Motorola Photon Q!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Photon Q Device Config: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-13.0
Kernel: https://github.com/arrrghhh/android_kernel_motorola_msm8960-common-twrp
DOWNLOAD:
Official Link
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Many thanks to @Dees_Troy, @helicopter88 & @bigbiff for helping get TWRP running, and of course thanks to @shabbypenguin for getting everything started on the device tree!
I highly advise the buglist and directions be reviewed!!
Thanks!!
Buglist​
**If you had an old version of TWRP installed before, MAKE SURE you 'Restore Defaults' under 'Settings' in TWRP**
Clock is off. Not sure why, seems unfixable.
Cannot use physical keyboard to type in Recovery...Obviously the on-screen kb works fine.
Directions:
** You must be unlocked in order to do this.**
2 choices after rooting. You can download TWRP Manager from the Play Store, menu, TWRP install & wait... (I do not provide support for this app FYI) or:
1. Reboot into fastboot (adb reboot bootloader, or turn off device, hold power + cam when booting and select 'fastboot')
2. Once in fastboot,
Code:
fastboot flash recovery twrp-2.7.1.2-asanti_c.img
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Works great! I used Goomanager
Edit: Works as in installs and boots. Touchscreen works, I have not tested the actual functions as of yet.
Tried to do a backup to external SD, it seems to have done it but after the loading bar finished I got the initial blue and black logo and couldn't get out of it. Had to 3 button reboot. Can't find the backup.
KitsunePaws said:
Works great! I used Goomanager
Edit: Works as in installs and boots. Touchscreen works, I have not tested the actual functions as of yet.
Tried to do a backup to external SD, it seems to have done it but after the loading bar finished I got the initial blue and black logo and couldn't get out of it. Had to 3 button reboot. Can't find the backup.
Click to expand...
Click to collapse
Hrm. I'll look into that... I think I've only done a backup to internal SD as my external is ridiculously full.
Edit - just did a backup of boot to the external, worked just fine. Perhaps wait a bit? How long did you wait, and what were you backing up?
Edit 2 - ok, perhaps I jumped the gun. "Worked" doesn't quite describe it... I have the TWRP folders for the backup, but there's no backup file in there. Strange... Perhaps because I backed up only boot. I'll try again with less junk on the card and do a full backup...
arrrghhh said:
Hrm. I'll look into that... I think I've only done a backup to internal SD as my external is ridiculously full.
Edit - just did a backup of boot to the external, worked just fine. Perhaps wait a bit? How long did you wait, and what were you backing up?
Click to expand...
Click to collapse
Just went with the default settings, I didn't wait that long after the progress bar went away it went back to a team logo, I let it sit for about a minute and then reset it. Trying again.
Ran through it again, it took a while backing up /data. (398 megs). The bar filled all the way up though it still said "... Backing up /data" Sitting at the teamwin logo again, it's been on this image for 4 minutes at this point (Went to the logo at 6:09). ( Now it's blinking. And now it reset. These could have been caused by my touching the screen. I think the logo is getting "stuck" ). Is the progress bar based on a timer or events?
Also, it made the TWRP folder on the internal SD regardless of the fact I told it external. I did notice that the backup path during said "/sdcard" and not "/mnt/external1". The folder does not contain a backup.
KitsunePaws said:
Just went with the default settings, I didn't wait that long after the progress bar went away it went back to a team logo, I let it sit for about a minute and then reset it. Trying again.
Ran through it again, it took a while backing up /data. (398 megs). The bar filled all the way up though it still said "... Backing up /data" Sitting at the teamwin logo again, it's been on this image for 4 minutes at this point (Went to the logo at 6:09). ( Now it's blinking. And now it reset. These could have been caused by my touching the screen. I think the logo is getting "stuck" ). Is the progress bar based on a timer or events?
Also, it made the TWRP folder on the internal SD regardless of the fact I told it external. I did notice that the backup path during said "/sdcard" and not "/mnt/external1". The folder does not contain a backup.
Click to expand...
Click to collapse
Indeed.
I am in the same "stuck" situation as you now. For the meantime, it seems backing up to external SD does NOT work... I tested backup and restore, but only to internal SD. I saw that my external didn't have enough space, and wrote it off as enough... Apologies for not thoroughly testing that.
arrrghhh said:
Indeed.
I am in the same "stuck" situation as you now. For the meantime, it seems backing up to external SD does NOT work... I tested backup and restore, but only to internal SD. I saw that my external didn't have enough space, and wrote it off as enough... Apologies for not thoroughly testing that.
Click to expand...
Click to collapse
No worries, that's what makes XDA the place that it is ^-^. If I expected perfection I would buy an iPh.... couldn't do it with a straight face.
OK, the issue with external SD should be fixed. However, I don't have the ability to push the changes to GooManager, so you'll have to flash manually until it's updated on GooManager (I'll let you know )
Edit - to be clear, you cannot use GooManager or the official link right now. Please use 'mirror 1' and manually update in order to fix the external SD issue (until it's officially updated).
Alrighty, Dees_Troy said it is officially updated. I can see the update on the official link - but I'm not sure how on GooManager you update - if you just click 'check for updates'? That seems to only check on ROM updates, but I could be wrong.
Please let me know how it goes! If you experience any issues, etc.
Edit - seems you just do the same as when it was initially installed... Menu -> Install OpenRecoveryScript & wait... then reboot to recovery.
Also, if you notice - TWRP is now 2.2.2.2 - yes, a whole lotta 2's... but that last .2 is the Q!! Congrats, we're official!
Aweesssommeee....
2.2.2.2 is finally showing up in goo
New SD path seems to be working. Any idea what driver it tried to install?
Looks like the logo issue is fixed too, grats.
KitsunePaws said:
New SD path seems to be working. Any idea what driver it tried to install?
Looks like the logo issue is fixed too, grats.
Click to expand...
Click to collapse
Glad it's workin for ya.
Driver? Not sure what you're talking about... there is ADB in recovery, if that's what you mean...
arrrghhh said:
Glad it's workin for ya.
Driver? Not sure what you're talking about... there is ADB in recovery, if that's what you mean...
Click to expand...
Click to collapse
Hmm, maybe I'm just going crazy, when it booted into recovery I got a dialog box that it was trying to install "asanti" and didn't have the driver, I've got the motorola app installed and adb works normally. Probably just a fluke.
KitsunePaws said:
Hmm, maybe I'm just going crazy, when it booted into recovery I got a dialog box that it was trying to install "asanti" and didn't have the driver, I've got the motorola app installed and adb works normally. Probably just a fluke.
Click to expand...
Click to collapse
Huh... perhaps when the device was 'in limbo'. I forced mine into limbo a few times messing with the kernel yesterday, and it did indeed create a bunch of new devices in Windows - some installed correctly, but adb didn't exactly work...
Hopefully no more of that on TWRP! I have run thru the gambit and the only outstanding fixable bugs are probably going to be the mass storage and the physical keyboard - which will probably take some time. I don't think the clock issue is fix-able...
Let me know if you guys find anything else broken. So far it has all worked for me!
Anyone know how long it's supposed to take to install thru goomanager?
Sent from my XT897 using xda premium
tetrabyt said:
Anyone know how long it's supposed to take to install thru goomanager?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Mine took no longer than 2-3 minutes from start to finish
KitsunePaws said:
Mine took no longer than 2-3 minutes from start to finish
Click to expand...
Click to collapse
Same. It was REALLY fast over wifi.
I must be missing something. I sat and watched it say installing recovery for about 15minutes. Had to keep touching the screen to keep it awake... Will try again.
Edit: it just took about 40seconds.. Thanks. It works now.
Sent from my XT897 using xda premium
tetrabyt said:
Edit: it just took about 40seconds.. Thanks. It works now.
Click to expand...
Click to collapse
Nice, glad it works for you!
So I've got 3 thanks on the first post, and I think 2 people have responded that they've installed it (with a third 'approving' of it )... but 60+ downloads? Is it just working that well that everyone forgets this thread exists? Hahahaha!
Well, I hope it is working well for everyone. Enjoy!
Public service announcement: Official cm-12.0 nightlies for Photon Q have been enabled.
Download link: http://download.cyanogenmod.org/?device=xt897
Gapps (use gapps-lp-...): http://d-h.st/users/dhacker29/?fld_id=27426#files
Recovery TWRP 2.8.5.0 for xt897: http://d-h.st/2e6S
Device specific source repos:
https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-12.0
https://github.com/CyanogenMod/android_device_motorola_msm8960_jbbl-common/tree/cm-12.0
https://github.com/CyanogenMod/android_device_motorola_qcom-common/tree/cm-12.0
https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-12.0
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
New features with caveats:
f2fs file system for /data and /cache partition can be used now.
You can switch to it in TWRP (don't forget to backup data and also the content of internal sdcard before changing the /data file system to f2fs in TWRP).
GSM users (SIM card mod):
Please switch the Settings>Mobile networks>Preferred network type to 'GSM/WCDMA auto' or 'GSM/WCDMA preferred' from 'Global' for correct modem functionality on GSM networks.
Known issues:
- USB audio output (analogue) via USB>audio Y-cable (Motorola Car Dock/EMU audio) is not working correctly yet
- USB audio DACs/sound cards connected as USB OTG peripheral do not work correctly yet
Awsom thank you
Planned a clean install today and just checked gapps where up to date. Just to find out cm 12.0 is out
nice
Edit:
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for for /dev/block/platform/msm_sdcc.1/by-name/userdata
detected filesystem ext4 for for /dev/block/platform/msm_sdcc.1/by-name/system
Click to expand...
Click to collapse
can I Ignore that, since update went successfully?
EDIT2
Somehow /system partition got broken had to install twrp recovery (from first post) and reformat /system partition with it.
---------- Post added at 12:50 PM ---------- Previous post was at 11:59 AM ----------
kabaldan said:
[...]
New features with caveats:
f2fs file system for /data and /cache partition can be used now.
You can switch to it in TWRP (don't forget to backup data and also the content of internal sdcard before changing the /data file system to f2fs in TWRP).
[...]
Click to expand...
Click to collapse
What are those caveats or hat are the benificials?
Thanks in advance
kecksk0enig said:
Awsom thank you
Planned a clean install today and just checked gapps where up to date. Just to find out cm 12.0 is out
nice
Edit:
can I Ignore that, since update went successfully?
EDIT2
Somehow /system partition got broken had to install twrp recovery (from first post) and reformat /system partition with it.
Click to expand...
Click to collapse
You have to use recovery with full selinux support.
What are those caveats or hat are the benificials?
Thanks in advance
Click to expand...
Click to collapse
Caveat is that there's no option in TWRP to backup the internal emulated sdcard (data backups skip /data/user folder where the internal sdcard resides) but when changing from etx4 to f2fs, the entire data partition has to be formatted.
Another thing is that you have to use a recovery with f2fs support in kernel, which is currently only the TWRP 2.8.5.0 linked above or CM recovery that comes with CM12 (its installation is however disabled by default, can be enabled under Develeper options.)
Benefit of f2fs compared to ext4 is faster I/O, more responsive device and higher benchmark results.
My Antutu score with f2fs (run only once as I'm not that interested in benchmarks) was 20694 (Storage I/O 719, Database I/O 630).
installing it right now, be back soon with reports of first impressions
- video cam doesnt work
- music app doesnt rotate to landscape and i get a lot of errors saying "music doesnt work anymore"
ill keep testing..
November91 said:
installing it right now, be back soon with reports of first impressions
- video cam doesnt work
- music app doesnt rotate to landscape and i get a lot of errors saying "music doesnt work anymore"
ill keep testing..
Click to expand...
Click to collapse
video recording seems to be working good
but I can't launch camera app by long-pressing the camera button, even though I got a tactile feedback...
palmwangja said:
video recording seems to be working good
but I can't launch camera app by long-pressing the camera button, even though I got a tactile feedback...
Click to expand...
Click to collapse
I think this is also an "issue" with CM11 because none of the other JBBL devices have a dedicated camera button.
Also, I think you mean "haptic" feedback. Tactile is the type of feedback having a great keyboard provides. Haptic feedback is vibration
long-press camera to launch cam app doesnt work for me either.
i'm also experiencing a lot of trouble with my wifi, it connects only occationally, but most of the time its offline
arrrghhh said:
I think this is also an "issue" with CM11 because none of the other JBBL devices have a dedicated camera button.
Also, I think you mean "haptic" feedback. Tactile is the type of feedback having a great keyboard provides. Haptic feedback is vibration
Click to expand...
Click to collapse
It's weird, I didn't have any problem with the camera-button launch on CM11....
---------- Post added at 01:40 AM ---------- Previous post was at 01:36 AM ----------
Up until CM11, I replaced keypad_8960.kl and keypad_8960.kcm to customize my keyboard, but CM12 didn't want to let me do that?
I double-checked but no-effect at all....
1. I really need to replace SYM with Search just to re-enable Quick Launch functionality.
2. CAPS for Shift, and Shift for CTRL.
Hi I am experiencing random wifi disconnects.
Catlog attached: http://pastebin.com/qV6kZfyT
Any advise? I allready changed to different wifi channels and also reinstalled cm12 (with reformat of course)
Ty
Everything seems to be working fine for the most part, although battery usage seems to be rather high (with wifi and my screen on, it lost ~1% every 3 minutes while plugged in).
palmwangja said:
It's weird, I didn't have any problem with the camera-button launch on CM11....
---------- Post added at 01:40 AM ---------- Previous post was at 01:36 AM ----------
Up until CM11, I replaced keypad_8960.kl and keypad_8960.kcm to customize my keyboard, but CM12 didn't want to let me do that?
I double-checked but no-effect at all....
1. I really need to replace SYM with Search just to re-enable Quick Launch functionality.
2. CAPS for Shift, and Shift for CTRL.
Click to expand...
Click to collapse
Oops, never mind.
layout file we used for KitKat and before does not necessarily work well with Lollipop.
You have to recreate them.
palmwangja said:
Oops, never mind.
layout file we used for KitKat and before does not necessarily work well with Lollipop.
You have to recreate them.
Click to expand...
Click to collapse
wrt Camera,
install Motorola Camera apk prior to version 4: you can solve two problems at once
1. you can save directly to SD card
2. you can launch via the shutter button
I tried version 4 & 5 which employed material design, but it fc'd with the following error:
java.lang.RuntimeException: createContext failed: EGL_BAD_ATTRIBUTE
at android.opengl.GLSurfaceView$EglHelper.throwEglException(GLSurfaceView.java:1192)
at android.opengl.GLSurfaceView$EglHelper.throwEglException(GLSurfaceView.java:1183)
at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:1033)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1400)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1239)
Click to expand...
Click to collapse
Here is the working version : http://www.ibtimes.co.uk/moto-x-2nd-gen-stock-camera-gallery-apps-moto-g-how-install-1465213
but you can use the most recent moto gallery though : http://forum.xda-developers.com/moto-g/themes-apps/apps-motorola-camera-gallery-apps-t2965282
kabaldan said:
Yes, you can restore a data backup made from ext4 file system to the new f2fs file system in TWRP.
Click to expand...
Click to collapse
I tried that and it did not work for me. I used TWRP 2.8.5.0, installed CM12 on ext4, installed my apps, did a backup, changed to f2fs and then restored my backup. TWRP complained about the filesystem-change (something like "backup was made on ext4, it may not boot eventually") but restored my data.
The next boot took very long and then the "Android is upgrading" window came, telling me it is updating >170 apps. That's about twice as much as normal. When that finished I got many FCs and not a single non-system app was working. Starting it from the launcher gave me a FC every time.
I tried it two times, same result.
I even have some more problems with F2FS. Under heavy usage it corrupted my filesystem three times in two days. It starts with errors during app-install (error-codes 500, 503, 506 and/or 509, as far as I remember). Restoring these apps with Titanium doesn't work either.
Then there will be an inaccessible folder in /data/app/ with the name of the app causing the install errors. You can find out which folder it is easily by booting into TWRP and see the messages. It will tell you "Unable to stat /data/app/appname". Sometimes also something called /data/system/dropbox-[randomnumber] has the same error (and I don't have dropbox installed!).
Then it is getting worse and worse. You won't see this folder with normal file managers, but it will show up in the console with "ls -la". You can't remove this folder with "rm -rf" on the console, even with superuser rights. You can't remove the folder in TWRP because you can't select it. Wiping /data does not work, neither, because it will only remove all folders and files but can't remove this broken thing. It's also not possible anymore to make and restore backups. Do a filesystem check will result in an error and an unbootable system. Save with "restore permissions".
The only thing working is changing the filesystem to do a full format and then change it back to f2fs and then do a clean install. Until it happens again.
I switched back to ext4 now for /data and /cache and everything works again But f2fs felt great, it was responding faster.
tobby88 said:
I tried that and it did not work for me. I used TWRP 2.8.5.0, installed CM12 on ext4, installed my apps, did a backup, changed to f2fs and then restored my backup. TWRP complained about the filesystem-change (something like "backup was made on ext4, it may not boot eventually") but restored my data.
The next boot took very long and then the "Android is upgrading" window came, telling me it is updating >170 apps. That's about twice as much as normal. When that finished I got many FCs and not a single non-system app was working. Starting it from the launcher gave me a FC every time.
I tried it two times, same result.
I even have some more problems with F2FS. Under heavy usage it corrupted my filesystem three times in two days. It starts with errors during app-install (error-codes 500, 503, 506 and/or 509, as far as I remember). Restoring these apps with Titanium doesn't work either.
Then there will be an inaccessible folder in /data/app/ with the name of the app causing the install errors. You can find out which folder it is easily by booting into TWRP and see the messages. It will tell you "Unable to stat /data/app/appname". Sometimes also something called /data/system/dropbox-[randomnumber] has the same error (and I don't have dropbox installed!).
Then it is getting worse and worse. You won't see this folder with normal file managers, but it will show up in the console with "ls -la". You can't remove this folder with "rm -rf" on the console, even with superuser rights. You can't remove the folder in TWRP because you can't select it. Wiping /data does not work, neither, because it will only remove all folders and files but can't remove this broken thing. It's also not possible anymore to make and restore backups. Do a filesystem check will result in an error and an unbootable system. Save with "restore permissions".
The only thing working is changing the filesystem to do a full format and then change it back to f2fs and then do a clean install. Until it happens again.
I switched back to ext4 now for /data and /cache and everything works again But f2fs felt great, it was responding faster.
Click to expand...
Click to collapse
Interesting.
I had no trouble to restore the data from ext4 TWRP data backup to the newly created f2fs userdata file system.
And I haven't experienced any data corruption since the switch to f2fs so far...
kabaldan said:
Interesting.
I had no trouble to restore the data from ext4 TWRP data backup to the newly created f2fs userdata file system.
And I haven't experienced any data corruption since the switch to f2fs so far...
Click to expand...
Click to collapse
Um... no problem at all on my side either.
f2fs migration and data restore were both very smooth and no pain at all.
Overall, CM12 experience was way better than what I originally expected. with an antutu 20K > score.
CPU Governor setup doesn't seem to be sticky after reboot, it comes back to 'interactive' whenever I set them up for others.
I am not able to disable the LED light when the battery is being charged.
Do I overlook some option?
palmwangja said:
CPU Governor setup doesn't seem to be sticky after reboot, it comes back to 'interactive' whenever I set them up for others.
Click to expand...
Click to collapse
Confirm that.
Loader009 said:
I am not able to disable the LED light when the battery is being charged.
Do I overlook some option?
Confirm that.
Click to expand...
Click to collapse
My LED settings are still working out as expected by probably having inherited the value from the previous installation of CM11.
CM12 simply lacks the settings dialog?
@palmwangja, the settings dialog is there but I cannot set the color (completely missing), pulse length and speed (both are there but greyed out). (Well, the last two settings have also been greyed out in CM11.)
So the settings are kind of useless. We are only able to enable/disable "battery light" and "pulse if battery low".
But I think it is just a CM12 issue being in early development. It will probably be fixed in the next few months.
palmwangja said:
CPU Governor setup doesn't seem to be sticky after reboot, it comes back to 'interactive' whenever I set them up for others.
Click to expand...
Click to collapse
looks like CPU Governor setting section gone for a while. since 0221 nightlies.