Since the latest updates to our Eclipse and CM7 have the ICS Transitions included, There is really no more need for this. Unless you want to add it to a different ROM that doesnt have them. In that case, use the link to the Original thread. Thanks
I came across this little tool in my quest for ICS transitions. This worked for me so I decided to share with everyone in the X2 forum. I only tried this on CM7 but it should work for all ROMs since it is using your own framework-res and SystemUI files. Before starting, I believe this is only for windows computers due to the fact that the patcher is a .exe file. But if you know how to run these files in other operating systems then you are good. Backup your ROM before flashing. I'm not responsible if you end up having to SBF.
All you need to do to get this to work for you is:
1. Download the patcher to your desktop here: http://forum.xda-developers.com/showpost.php?p=19285951&postcount=41
2. Extract files from .zip
3. Copy your framework-res.apk and your SystemUI.apk from your phone to your desktop.
4. Place your framework-res.apk in the res/framework folder
5. place your SystemUI.apk in the res/app folder
6. Run the patcher.exe included in the file
7. After maybe 10 minutes or less, it will produce two zip files. One is the ICS transitions and the other is, I'm assuming, a backup in case you decide you want your old transitions back.
8. Flash the .zip with the ICS transitions to your device in bootstrap recovery.
9. Restart and you should have the new transition effect.
I hope this is helpful to everyone. It was for me. Thanks to Achep, capez and DaxIΠFIΠITY for making this awesome patcher.
UPDATE: I have attached the two .zip files that I created using this patcher tool. I'm not 100% but I'll bet its safe to say that these are ONLY for the CM7 ROM for the X2 since I used the two files from that ROM to make it. I don't suggest flashing this on any other ROM than CM7 for DX2. If you want to try this on another ROM, use the patcher tool in the link above and use the files from your own ROM. There are two files. One is the ICS transitions and the other is an "undo" zip that should set you back to normal.
WARNING: It has been reported that if you have used metamorph to modify your theme in any way, you may get a bootloop If you flash my files. If you have used metamorph, I suggest using the patcher tool and creating your own file rather than flash mine.
Maybe u could upload the zip? Not everyone has a decent PC....
whoa look at that....
king..kranium said:
Maybe u could upload the zip? Not everyone has a decent PC....
whoa look at that....
Click to expand...
Click to collapse
Attached is the file I flashed to my phone. I am on CM7 and I suggest if you are on any other ROM, to follow the steps in the first post with your own files. And I am just going to repeat myself and say backup before flashing. Good luck.
jsgraphicart said:
Attached is the file I flashed to my phone. I am on CM7 and I suggest if you are on any other ROM, to follow the steps in the first post with your own files. And I am just going to repeat myself and say backup before flashing. Good luck.
Click to expand...
Click to collapse
What exactly are the ics transitions?
Sent from my MB870 using XDA
Pulled my two files from Eclipse 2.1 and when I run the patcher program, I get the following:
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, :\Temp\APKTOOL672838009714900771.tmp, -x, -S, D:\Downloads\Droid\ICS-easy-patcher\res\framework\framework-res\res, -M, D:\Downloads\Droid\ICS-easy-patcher\res\framework\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\T
emp\APKTOOL672838009714900771.tmp, -x, -S, D:\Downloads\Droid\ICS-easy-patcher\r
es\framework\framework-res\res, -M, D:\Downloads\Droid\ICS-easy-patcher\res\fram
ework\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
ERROR WHEN COMPILING!!! - framework-res.apk
kennyb6 said:
What exactly are the ics transitions?
Sent from my MB870 using XDA
Click to expand...
Click to collapse
Here is a video showing them:
http://www.youtube.com/watch?v=vf1U_30Ngfk
iBolski said:
Pulled my two files from Eclipse 2.1 and when I run the patcher program, I get the following:
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, :\Temp\APKTOOL672838009714900771.tmp, -x, -S, D:\Downloads\Droid\ICS-easy-patcher\res\framework\framework-res\res, -M, D:\Downloads\Droid\ICS-easy-patcher\res\framework\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\T
emp\APKTOOL672838009714900771.tmp, -x, -S, D:\Downloads\Droid\ICS-easy-patcher\r
es\framework\framework-res\res, -M, D:\Downloads\Droid\ICS-easy-patcher\res\fram
ework\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
ERROR WHEN COMPILING!!! - framework-res.apk
Click to expand...
Click to collapse
Thats odd. Well like I said, I only tried this on CM7. Maybe Eclipse's framework is different? The thread I got this from said it was for all ROMs so I dont know why it wouldn't work for Eclipse as well. What OS are you using. I did this on an XP machine. I dont know if that would make a difference.
jsgraphicart said:
Thats odd. Well like I said, I only tried this on CM7. Maybe Eclipse's framework is different? The thread I got this from said it was for all ROMs so I dont know why it wouldn't work for Eclipse as well. What OS are you using. I did this on an XP machine. I dont know if that would make a difference.
Click to expand...
Click to collapse
It's an XP machine as well. I'm sure the APKs are different since Eclipse is based on the stock blur ROM while CM7 is AOSP.
No biggie. Thanks for posting this.
iBolski said:
It's an XP machine as well. I'm sure the APKs are different since Eclipse is based on the stock blur ROM while CM7 is AOSP.
No biggie. Thanks for posting this.
Click to expand...
Click to collapse
Sorry it didnt work for you. I wonder what other ROMs it does and doesnt work with. I may have to change the thread title.
I just flashed this and I'm running into an issue.
Before I flashed I made a Back Up like you suggested. After that was done I wiped cache and dalvik. I flashed the .zip you posted and wiped cache and dalvik again. I rebooted back into CM7 and found that some transitions were laggy so I wanted to go get my back up. When I tried to get into the CM7 System recovery mode it just shuts off my phone. Any ideas?
I flashed it this morning and had no problems. I did decide to go back to what I had before and had no problems restoring my nano back up. I am using cm7 as well.
Bohnsta said:
I just flashed this and I'm running into an issue.
Before I flashed I made a Back Up like you suggested. After that was done I wiped cache and dalvik. I flashed the .zip you posted and wiped cache and dalvik again. I rebooted back into CM7 and found that some transitions were laggy so I wanted to go get my back up. When I tried to get into the CM7 System recovery mode it just shuts off my phone. Any ideas?
Click to expand...
Click to collapse
I dont think this should mess with the CM7 System Recovery. And I dont know if wiping that many times had anything to do with it but when I installed this, I didnt wipe anything. Just flashed and rebooted. It didnt mess up your phone did it? If your phone is on, make sure your super user app is granting root permissions to the CM7 app. Thats the only thing I can think of that might be keeping you from booting into system recovery.
Travisdroidx2 said:
I flashed it this morning and had no problems. I did decide to go back to what I had before and had no problems restoring my nano back up. I am using cm7 as well.
Click to expand...
Click to collapse
Just wondering, did you create the .zip yourself with the patcher or use the file I uploaded? Just wanting to know if my .zip works for others.
jsgraphicart said:
Just wondering, did you create the .zip yourself with the patcher or use the file I uploaded? Just wanting to know if my .zip works for others.
Click to expand...
Click to collapse
I used the .zip file you made wiped cache and flashed with bsr. Used it for a while with no issues and worked as stated.
Travisdroidx2 said:
I used the .zip file you made wiped cache and flashed with bsr. Used it for a while with no issues and worked as stated.
Click to expand...
Click to collapse
Thanks. At least I know it works for others now. So did you just not like the transition effects?
jsgraphicart said:
I dont think this should mess with the CM7 System Recovery. And I dont know if wiping that many times had anything to do with it but when I installed this, I didnt wipe anything. Just flashed and rebooted. It didnt mess up your phone did it? If your phone is on, make sure your super user app is granting root permissions to the CM7 app. Thats the only thing I can think of that might be keeping you from booting into system recovery.
Click to expand...
Click to collapse
No my phone is fine and su granted permission to cm7 recovery. It is all good in hood though. I just SBF'd to 2.3.4 earlier so it's not a hassle to do it again!
Sent from my Kindle Fire using XDA
I actually thought it was cool. I think I am just so used to the way I have had it for so long I went back. But I will most likely try it again at some point.
Bohnsta said:
No my phone is fine and su granted permission to cm7 recovery. It is all good in hood though. I just SBF'd to 2.3.4 earlier so it's not a hassle to do it again!
Sent from my Kindle Fire using XDA
Click to expand...
Click to collapse
Sorry to hear that. I have no idea why your CM7 System Recovery would be messed up. If you get everything back in order maybe try again. Travisdroidx2 reported it working for him.
jsgraphicart said:
I dont think this should mess with the CM7 System Recovery. And I dont know if wiping that many times had anything to do with it but when I installed this, I didnt wipe anything. Just flashed and rebooted. It didnt mess up your phone did it? If your phone is on, make sure your super user app is granting root permissions to the CM7 app. Thats the only thing I can think of that might be keeping you from booting into system recovery.
Click to expand...
Click to collapse
This happened to me as i did the same... updated to susuperuser and Viola problem solved
whoa look at that....
jsgraphicart said:
Sorry to hear that. I have no idea why your CM7 System Recovery would be messed up. If you get everything back in order maybe try again. Travisdroidx2 reported it working for him.
Click to expand...
Click to collapse
I always wipe partition and dalvik before flashing a theme. And when I restored my back up I always wipe data and cache before restoring. Then before I reboot I flash rerecovery for CM7 and reboot. I had no issues at all and it worked just as he said.
Related
Hi, I'm a new root user, and I was trying to get LiveWallpapers to work on my rooted Droid Eris. I flashed the .zip file and the package apparently came with the Nexus Lockscreen also. I later discovered that LiveWallpapers just won't work on a Sense ROM, but I'd like to revert back to the Sense Lockscreen if possible. Can anyone help me with this? Thanks.
mcfly2524 said:
Hi, I'm a new root user, and I was trying to get LiveWallpapers to work on my rooted Droid Eris. I flashed the .zip file and the package apparently came with the Nexus Lockscreen also. I later discovered that LiveWallpapers just won't work on a Sense ROM, but I'd like to revert back to the Sense Lockscreen if possible. Can anyone help me with this? Thanks.
Click to expand...
Click to collapse
did you do a nandroid backup before flashing the .zip file? this is a must must must lol if you didnt the easiest way is to boot to recovery wipe data and dalvik and reflash and and make sure to do a backup. and what sense ROM are you using that doesnt support lwp
Funnyface19 said:
did you do a nandroid backup before flashing the .zip file? this is a must must must lol if you didnt the easiest way is to boot to recovery wipe data and dalvik and reflash and and make sure to do a backup. and what sense ROM are you using that doesnt support lwp
Click to expand...
Click to collapse
You can also pull HtcLockScreen.apk out of your rom's zip file and push it to /system/app/
Will this just revert back to original factory settings?
Oh, I guess i used the Stock Android 2.1 w/ Root Access.
Perhaps I should just load different ROM.
I found the HtcLockScreen.apk in the zip file, and threw it on my SD card, but i'm not sure what to do now. I tried using eoeAppInstaller but it said Install not successful. Not sure I quite understand what you mean by pushing the file to /system/app/
mcfly2524 said:
I found the HtcLockScreen.apk in the zip file, and threw it on my SD card, but i'm not sure what to do now. I tried using eoeAppInstaller but it said Install not successful. Not sure I quite understand what you mean by pushing the file to /system/app/
Click to expand...
Click to collapse
no need to put it on your sd card its useless there if im correct and if anyone more professional than me can verify you need to use command promt to run the adb app in your android sdk file and if thats the case search the threads for adb to answer your question
try here there are several that are based on sense and will let u set livewallpaper and have the slide lock that you seek just read up on them
OK! This isn't as simple as it was for BlaY0's ROM. I think the reason is that some people are on nightlies which are stable, so they don't bother using the "official" stable one, or that people use a version that's slightly after 6.1, and could be though of as 6.1.1 (if you have the option for a rotary lockscreen, that's you). This means that frameworks differ slightly, which means I can't a one-zip-for-all type release. There are 2 ways round this:
You make it yourself by going to circle.glx.nl
I do it in a metamorph
I have made a metamorph for the fly-in animation, see here: http://forum.xda-developers.com/showpost.php?p=10217215&postcount=18
This is kind of in testing, but it should work. Let me know.
this animation work on the stock rom?
lollazzo said:
this animation work on the stock rom?
Click to expand...
Click to collapse
Only on cyanogenmod. And it might even not work on that, I'm not sure
Swyped from my HTC Legend
How did you iplemented those window animations?
Did you the Ultimate Online Kitchen? http://circle.glx.nl/
Cause I tried that once but it didn't work :s
Edit: Nevermind, just implemented it in CM 7.0 and it works perfectly
can you do this with bounce animation?
edit:I made it and it functions..in cm 7.0
It gave me boot loop on CM7 ... !
Aminmvb said:
It gave me boot loop on CM7 ... !
Click to expand...
Click to collapse
Did you wiped Dalvik Cache ?
matn013 said:
Did you wiped Dalvik Cache ?
Click to expand...
Click to collapse
Yep , even with adb !
This is for CM 6.1
I am on 6.1, with wiped cache and bootloops. A disclaimer would have been nice. I trusted this was tested and functional since it's not in the development section
greenolive said:
I am on 6.1, with wiped cache and bootloops. A disclaimer would have been nice. I trusted this was tested and functional since it's not in the development section
Click to expand...
Click to collapse
Well, they are tested on my phone. I've pulled them for now, and I'll try again and test a little more thoroughly.
If you didn't backup you can go grab framework-res.apk from the CM-6.1 zip file that you installed from (if you're anything like me it'll still be on your SD card) and push it back to your device with ADB. If you're S-ON you will need to be in recovery mode. Make sure system is mounted (there's an option for this in the "partitions" menu) That will fix the bootloop issue.
Once again, I'm very sorry about this, I'll look into it and upload amended versions. Or, if you feel like being bold you can make it yourself: circle.glx.nl
EDIT:
Attached is a flashable zip that should get you back to normal I'd still wipe dalvik-cache with this one
EDIT 2:
OP updated with fixed versions
EDIT 3:
Things are still screwed for some people, EDIT 1 has been undone
Yup, thanks for the tip. I pushed it back and its booting fine. Well of course you can't test it on more devices than your own. My post might seem a bit cranky. My bad... Grumpy because of hunger I suppose
But what super-special stuff did you do for it to work on your device?
greenolive said:
Yup, thanks for the tip. I pushed it back and its booting fine. Well of course you can't test it on more devices than your own. My post might seem a bit cranky. My bad... Grumpy because of hunger I suppose
But what super-special stuff did you do for it to work on your device?
Click to expand...
Click to collapse
You're completely entitled to be cranky, I screwed up. Again. Try with the new version I posted in the OP. It should be better. And I tend to do stuff live, without all the flashing of zips, so maybe I missed something the first time 'round. (/system overlay, restarting the android framework and ADB)
Will try in a sec!
Well, S-OFF can cause f***-ups
greenolive said:
Will try in a sec!
Well, S-OFF can cause f***-ups
Click to expand...
Click to collapse
Ha haa, S-OFF was done AFTER these MODs. But I still use an overlay on /system for a lot of stuff.
Alright, I tried the new zip and its booting up fine. And the fly-in graphics are working. Too bad all I see are all running processes being killed. Over and over again. Something is not what it should. Still progress
EDIT: Even the zip that should restore framework-res.apk causes the killing of processes. Restored the one from the 6.1 zip and its fine now
Working fine for me. This is nifty, got any other animations up your sleeves?
Edit: Oh wow, just realized how many this changes. Nice.
@greenolive. This is strange. I've just made a metamorph, but I gotta test it on a fresh install of CM.
@speedyink, there are more. I just need to find a way to release these for CM so that they work for everyone.
EDIT:
==================================================================================
Ok, I have made a metamorph Do not try to flash this zip. In order to use this you need either S-OFF or /system overlay. This should be a little more forgiving with the specific build of CM you're using. It is attached to this post, and won't make it to the OP until I'm a little more confident. This IS tested. I wiped everything and installed a new version of CM just so I could test this without my other modifications affecting it.
In testing, I didn't need to wipe dalvik-cache, but if you get problems do that before you complain at me
Ah, one more thing. You may wonder how this is any better than the zips I posted earlier. Well, as metamorph replaces the files it needs in your framework-res.apk, as opposed to replacing the whole apk (that's what the zips did), there is a smaller chance of errors caused by the the "wrong" framework.
i have cyanogen 6.1. for me the zip file got me into a boot loop and the metamorph did nothing. however i did manage to make it work by copying the anim folder from your zip file manually into my framewrok-res.apk file
I've been tried the metamorph version on CM7 nightlies and it worked on all of those roms .
Ty TGF.
I finally got superclean 2.8 voodoo to work right but now that want to flash touchwiz launcher and apps-from what I understand is just doing the same thing in cwm-it does not work.. It says I had installed the .zip but when I reboot nothing is changed. I even moved the .zips from the Touch Wiz folder on my sd card to the root of my sd card.. What am I doing wrong? As I'm unable to flash touchwiz onto my phone.. This is confusing me because I'm doing everything right, unless I broke something.
Slic|< said:
I finally got superclean 2.8 voodoo to work right but now that want to flash touchwiz launcher and apps-from what I understand is just doing the same thing in cwm-it does not work.. It says I had installed the .zip but when I reboot nothing is changed. I even moved the .zips from the Touch Wiz folder on my sd card to the root of my sd card.. What am I doing wrong? As I'm unable to flash touchwiz onto my phone.. This is confusing me because I'm doing everything right, unless I broke something.
Click to expand...
Click to collapse
Did you clear cache and dalvik before flashing tw zip? Tw should have been on your phone to start with, version comes with 2.8. Are you trying to over write the existing tw?
wideopn11 said:
Did you clear cache and dalvik before flashing tw zip? Tw should have been on your phone to start with, version comes with 2.8. Are you trying to over write the existing tw?
Click to expand...
Click to collapse
TW (the launcher) does not come with SC2.8. He obviously wants it back. Personally, I kinda like the TW launcher and have the zip sitting on my sd card, but haven't tried flashing it back yet. I suppose I should just to see if it works.
wideopn11 said:
Did you clear cache and dalvik before flashing tw zip? Tw should have been on your phone to start with, version comes with 2.8. Are you trying to over write the existing tw?
Click to expand...
Click to collapse
I have cleared dalvik cache and cache, including wiping data the first time. I'm no version 2.8 superclean has stock 2.3 gingerbread launcher??? :/ No tw... Tw comes as a patch... which apparently isn't working.
luigi1111 said:
TW (the launcher) does not come with SC2.8. He obviously wants it back. Personally, I kinda like the TW launcher and have the zip sitting on my sd card, but haven't tried flashing it back yet. I suppose I should just to see if it works.
Click to expand...
Click to collapse
It didn't work for me... including the other tw patches. :/ Let me know how it goes for you.
Slic|< said:
It didn't work for me... including the other tw patches. :/ Let me know how it goes for you.
Click to expand...
Click to collapse
You still have red CWM right? (ver. 2.5.x)
luigi1111 said:
You still have red CWM right? (ver. 2.5.x)
Click to expand...
Click to collapse
Yep using J133t cwm recovery for all red. :/ Did it work for you?
You are right. A no go. After it failed I thought perhaps it was permissions so I went into Terminal Emulator and ran fxpms under root: still nothing. Adrynalyne should probably be notified. Perhaps it's another scripting issue?
luigi1111 said:
You are right. A no go. After it failed I thought perhaps it was permissions so I went into Terminal Emulator and ran fxpms under root: still nothing. Adrynalyne should probably be notified. Perhaps it's another scripting issue?
Click to expand...
Click to collapse
He said it should work, I'm unsure why its not... and if thats the case you know anywhere else that we can download the TouchWiz launcher plus live wall paper, and the stock apparel including bloat? Cuz I did like some of the apps and wanted to try the games lol... And yeah Adrynalyne should be notified but I can't post on the developement part of the thread. I guess a PMT would be better than a thread?? Idk which one cuz I dont know which would be answered more. I hope not cuz he did say all patches and superclean where 2.5.x CWM only with edify scripts for 2.8 to work with 3.0 cwm AFTER you installed it via 2.5.x red cwm. :-/
Did you make sure you had the current .zip files from the new SuperClean thread? Some earlier ones had problems with installing on 2.8 and Adry had to update the files to work.
http://forum.xda-developers.com/showthread.php?t=983395
scarfman4 said:
Did you make sure you had the current .zip files from the new SuperClean thread? Some earlier ones had problems with installing on 2.8 and Adry had to update the files to work.
http://forum.xda-developers.com/showthread.php?t=983395
Click to expand...
Click to collapse
Correct. I redid the patches again. Make sure you have the latest copy from the thread.
Sent from my SCH-I500 using XDA App
scarfman4 said:
Did you make sure you had the current .zip files from the new SuperClean thread? Some earlier ones had problems with installing on 2.8 and Adry had to update the files to work.
http://forum.xda-developers.com/showthread.php?t=983395
Click to expand...
Click to collapse
Oh no. Ill try it though and report back. Thanks.
adrynalyne said:
Correct. I redid the patches again. Make sure you have the latest copy from the thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ok thanks, ill retry it and let you know. Also thanks for the quick reply. Keep up the good work. Also what is DRM for and can we use the vzw 3g tethering app? Cuz it gives me options I've never seen after closing the warning.
luigi1111 said:
TW (the launcher) does not come with SC2.8. He obviously wants it back. Personally, I kinda like the TW launcher and have the zip sitting on my sd card, but haven't tried flashing it back yet. I suppose I should just to see if it works.
Click to expand...
Click to collapse
You are correct, sorry I mixed up SC2.8 with DarkREVENGE. DarkREVENGE has a TW launcher included. I just use LPP.
wideopn11 said:
You are correct, sorry I mixed up SC2.8 with DarkREVENGE. DarkREVENGE has a TW launcher included. I just use LPP.
Click to expand...
Click to collapse
Ah it's cool haha. DarkREVENGE has the gtg tw launcher or CrushD's edited GTG Tw launcher?? You tried it yet, does it have working notification bubbles? Oh haha. I like the look of the new tw launcher very much, ever since froyo they actually made it much better looking.. especially with the sick color scheme. Reminds me of the Galaxy S2 which I'm guessing that's the direction they were headed.
EDIT: Now just need to get dem sick widgets from the Galaxy S2 ova to the Fascinate and my life would be set. Haha..
So I just realized that A2SD really corrupts your phone. Why?
Because every rom I use with A2SD ends up having the same problem over and over again, no matter what rom I'm using. And as a matter of fact, it's happening to me right now AGAIN after 3 weeks of recovering from a major one. Last one was worse because I couldn't wipe dalvik cache or flash any roms from CWM and had to completely reflash a 5 package with Odin.
Your phone will start turning off randomly. I myself just found my phone off WHILE CHARGING again. The common factor between all the roms I've been using is A2SD. No matter what script or mod I use. The fist time it happened to me was using Jusada's ICS final and now I'm all the way on The Myth 2.
I will still be using A2SD since I really need the extra space. My C++ compiler by itself is 60MB.
Just wanted to let you guys know, if it happened to you, you're gonna have to reflash a new rom all over again. If you can't wipe something from CWM before installing a rom, Odin is your fix.
Just want to make this clear, does your phone turn off completely or does it reboot?
QNBT said:
Just want to make this clear, does your phone turn off completely or does it reboot?
Click to expand...
Click to collapse
Off completely. When I press the home button, it only shows the charging icon and nothing more.
SuperAce609 said:
Off completely. When I press the home button, it only shows the charging icon and nothing more.
Click to expand...
Click to collapse
I've been using the INT2EXT4+ script for a few months(?) and I havent got in touch with this issue. You could try to go stock for a week (with your essential apps installed + another sdcard) and see if this occurs to confirm it, such a hassle though...
To me this doesn't really sound convincing if I were to be honest, mostly because it hasnt struck me (yet).
QNBT said:
I've been using the INT2EXT4+ script for a few months(?) and I havent got in touch with this issue. You could try to go stock for a week (with your essential apps installed + another sdcard) and see if this occurs to confirm it, such a hassle though...
To me this doesn't really sound convincing if I were to be honest, mostly because it hasnt struck me (yet).
Click to expand...
Click to collapse
I don't know. It keeps happening to me constantly. I just finished reflashing Myth 2 again. The script I was using before was INT2EXT+. Going to do the same thing all over again. I'm not sure if its the SD because this happened way back in the Jusada days and back then I had just recently bought my phone + SD.
Even while using S2E on CM7 and while I was using DT's A2SD when I first started using Myth 2. Not really sure how it's possible. This is my only theory.
Yep I also have issues with different A2SDs.
S2E
After a reboot my sd-ext is not mounted. Had to use Advance restore in CWM (sd-ext only)
Darktremor's A2SD
Random bootloop after a reboot. Had to completely restore CWM backup
INT2EXT/4
After a reboot, sd-card is only mounted as R/O. Had to use Advance restore in CWM (sd-ext only)
So every once in a while I always do nandroid back-ups. That's the only solution I know. But now I deleted scripts in my init.d specifically Adrenaline Engine because I noticed some of them has remount scripts at boot. I only left the default ones and the a2sd script. After a few reboots no problems so far. Hoping this will continue for a long time. :fingers-crossed:
I don't think that the matter is to be taken as drastically as in OP.
Using an a2sd script obviously puts your phone in the condition to be less stable than before, but some little steps will help you facing it.
1) If dalvik is moved to sd-ext by the script DON'T WIPE IT. It will result in phone not booting. If you are using INT2EXT script there is a flashable zip which wipes it in a secure way (just have a look at the Cronmod topic in this forum).
2) If the SD doesn't mount properly try taking it away and cleaning it (I think blowing at the SD and at the socket will do). It happened to me that the phone wasn't booting, no matter how many times I restarted it. After cleaning SD it was all right... and the same happened to a friend of mine.
3) Do frequent backups (at least once a week). You never know.
Hope I was helpful.
Sent from my Ace on Apocalypse Rom
I can safely assume that I was using a2sd far longer than you and for the 3-5 months I stuck with Apocalypse S2E and A2SD works perfectly with no problems .
Sent from Ursa's claws.
Im using Amarullz, is that what you're using?
Austin 3:16 says "I just whooped your ass". Sent from my Cooper running Gingerbread MIUI.
i've been using dt a2sd since the first time i use custom rom, it's a long time ago, no problem so far..
can honestly the problem isnt with the script i had this issue tons of times aswell with multiple roms.
something on your sd ext is corrupt format your sd card with mini partition tool and recreate an ext 4 using that aswell will sort the issue out
n btw i was getting bootloops and andriod force close alot before i formated
now using Amarullz tho its alot more stable
Jar3112 said:
I don't think that the matter is to be taken as drastically as in OP.
Using an a2sd script obviously puts your phone in the condition to be less stable than before, but some little steps will help you facing it.
1) If dalvik is moved to sd-ext by the script DON'T WIPE IT. It will result in phone not booting. If you are using INT2EXT script there is a flashable zip which wipes it in a secure way (just have a look at the Cronmod topic in this forum).
2) If the SD doesn't mount properly try taking it away and cleaning it (I think blowing at the SD and at the socket will do). It happened to me that the phone wasn't booting, no matter how many times I restarted it. After cleaning SD it was all right... and the same happened to a friend of mine.
3) Do frequent backups (at least once a week). You never know.
Hope I was helpful.
Sent from my Ace on Apocalypse Rom
Click to expand...
Click to collapse
1. I never wipe dalvik unless I'm flashing a new rom.
2. I've never had that problem.
3. Yeah, I told myself I was going to do that but I kept forgetting. Either way, if you do a backup, won't you save the to-be-corrupted files anyway?
CallMeVentus said:
I can safely assume that I was using a2sd far longer than you and for the 3-5 months I stuck with Apocalypse S2E and A2SD works perfectly with no problems .
Sent from Ursa's claws.
Click to expand...
Click to collapse
Then why meeeeeeeeee?! This is so unfair :'(
MrChaosDesire said:
Im using Amarullz, is that what you're using?
Austin 3:16 says "I just whooped your ass". Sent from my Cooper running Gingerbread MIUI.
Click to expand...
Click to collapse
No, I don't use CM roms anymore. I'm using INT2EXT.
Amni said:
can honestly the problem isnt with the script i had this issue tons of times aswell with multiple roms.
something on your sd ext is corrupt format your sd card with mini partition tool and recreate an ext 4 using that aswell will sort the issue out
n btw i was getting bootloops and andriod force close alot before i formated
now using Amarullz tho its alot more stable
Click to expand...
Click to collapse
So you're saying the problem is the ext partition that CWM creates? Ext 4 is better? But a lot of people make partitions off CWM and theirs still work fine. :/
SuperAce609 said:
1. I never wipe dalvik unless I'm flashing a new rom.
2. I've never had that problem.
3. Yeah, I told myself I was going to do that but I kept forgetting. Either way, if you do a backup, won't you save the to-be-corrupted files anyway?
Click to expand...
Click to collapse
You should take backups of your last perfectly working configuration, once you find it!
Sent from my Ace on Apocalypse Rom
Jar3112 said:
You should take backups of your last perfectly working configuration, once you find it!
Sent from my Ace on Apocalypse Rom
Click to expand...
Click to collapse
Hmm.. about to make a backup right now then. I was thinking of backing up a clean version of Myth 2 but I remembered to when I was already restoring my apps. I guess there's still time.
SuperAce609 said:
Hmm.. about to make a backup right now then. I was thinking of backing up a clean version of Myth 2 but I remembered to when I was already restoring my apps. I guess there's still time.
Click to expand...
Click to collapse
What's your sdcard ? And class ?
Sent from Ursa's claws.
I already used S2E, DT A2D, Link2SD and never had any problem like this.
But I'm facing a different but at the same time similar problem. By "similar" I mean that the problem also persists even flashing the ROM again, or flashing other ROMs (CM based ones).
WelI, I was testing CM 7.2 SIII Mod v2 ROM and after a reboot the PlayStore app disappeared. I did the 3 wipes, flashed the ROM again and it wasn't there either. Then I installed the Stock 2.3.6 with Odin and again flashed that same ROM and nothing again. Installed Stock 2.3.6 with Odin again, downloaded the latest CM7.2 from cyanogenmod website, flashed it, and guess what ? No PlayStore app! Now in every CM based ROM that I flash, PlayStore is missing. In Stock based ones there is no problem, it's always there.
CallMeVentus said:
What's your sdcard ? And class ?
Sent from Ursa's claws.
Click to expand...
Click to collapse
I'm using an 8GB class 4. How about you guys?
Already did the backup. I really hope it doesn't happen anymore. Everything is literally working flawlessly on my phone
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
jeff5347 said:
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
Click to expand...
Click to collapse
Well what ROM are you using for starters.
that might be important right.. .sorry.. its aokp 6
Ok. Well if you can get back into BSR, try and wipe the dalvik cache in the advance settings. I never use the fix permissions option. Maybe that did something to your device.
did that too. Still on the boot logo. is a sbf in order
jeff5347 said:
did that too. Still on the boot logo. is a sbf in order
Click to expand...
Click to collapse
Well I wouldnt see why it would do that if you just wiped cache and fixed permissions. Did you have any other mods on there? Were you using the patched CM7 BSR and not the original one?
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
jeff5347 said:
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
Click to expand...
Click to collapse
That one is fine to use on Eclipse. But pretty much any other ROM we have (CM7, CM9, CM10, AOKP, Paranoid Android and I think even MIUI), you need to use the CM7 BSR named "MOTODX2_Bootstrap-CM7-signed.apk" which is found in the CM7 thread. That may have been the problem.
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
jeff5347 said:
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
Click to expand...
Click to collapse
I think CM10 is more stable than any of the ICS ROMs. But with the stability, there comes other small issues that the ICS ROMs dont have. Its a trade off. Main issues of CM10:
1. Messing with bluetooth may cause phone to crash durring calls. Reboot fixes it until bluetooth is messed with again. (Might be fixed with an update)
2. Storage is in a different location. Not really an issue but its also swapped back to the original 4gigs for the internal. All your files will be flipped after using other ROMs for so long. (not a huge deal)
3. Due to the storage being moved around, apps that are stored on the SD card will disappear after reboot. (will probably be fixed in the future)
4. Flashing ROMs in recovery wont work. If any update comes out, you have to either SBF and update or nandroid back to ICS and update. (again, not a huge issue)
Other than that, I cant really think of any bad stuff. Its faster and I have no random reboots. I recommend it if you can live with the issues I mentioned which are honestly not bad.
Also, with the BSR files, in case you dont know already. When you are on stock 2.3.4, you first use the original BSR. Then when you flash CM10, you install the CM7 BSR.
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
jeff5347 said:
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
Click to expand...
Click to collapse
1. I use bluetooth every now and then but I never turn it off. It seems that toggling the bluetooth on and off or visa versa triggers the issue and a reboot fixes it again.
2. I forget what Eclipse had. Its been so long. But ever since CM7, the flip flop mod has been included in all the ROMs which meant you got your SD card (which the droid X2 comes with 8GB) as internal storage and the actual 4GB internal storage was turned into the "external storage." CM10 reverted back to the original 4GB internal and 8GB external.
3. Everything you download and install on your phone will usually be installed on the internal storage. I think if you have apps over a certain size (which isnt very many. Mostly games), they are installed on your SD card. Those are the ones the system has a problem reading after a reboot. the actual files you have downloaded from XDA will still be there. Just installed apps might disappear.
4. Not really sure what you are asking here. But if you get A2 installed and up and running and A3 comes out, You will pretty much need to start over. But for me, thats fine. I use Titanium Backup and restore everything after a wipe anyway. What data are you referring to?
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
jeff5347 said:
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
Click to expand...
Click to collapse
Honestly, I dont even know what MD5sum means. I'm not that tech smart. lol. I know thats the right file name though. And if you got it from here: http://goo.im/gapps you should be fine.
hahaha neither do i lol yea thats where i got it.. again thank you
No problem. If you have any other issues, just reply here and I'll help out.
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
jeff5347 said:
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
Click to expand...
Click to collapse
Pete's can be a PITA... If usb debug is enabled and unkown sources is checked just keep trying. I've had to "one click" 5 or 6 times before it works right. Close the program between tries. Also make sure your phone isn't in PC charge mode or anything.
Sorry for not updating this. After trying for 2 hrs I started trying everything. It turned out I had to use the cable that came w the dx2. No other cables worked
Sent from my MB870 using xda premium
Ah, my bad I should have read the time stamp. Anyway yea, the cable is a big deal (even though that sounds crazy.)
---------- Post added at 10:54 PM ---------- Previous post was at 10:43 PM ----------
Lol oh and btw MD5 checksums are
"The MD5 checksum for a file is a 128-bit value, something like a fingerprint of the file. There is a very small possibility of getting two identical checksums of two different files. This feature can be useful both for comparing the files and their integrity control."