Related
Hello guys, first I will like to thank all of you for supporting the forum and for helping me a lot. I been trying by far do the list below and I cant get it to work correctly in more then 20 attempts and Im afraid I will totally brick my vibrant.
Done Procedures;
I have ROOTed the Phone
BackUp all my files using Titanium
Flashed ClockWorkMod with Rom Manager
Flashed with ROM Bionix V 1.3.1
Delete Cache and Dalvik...
Rebooted system
At that point everything is good but once I install a kernel I start having problems with the SD recognition by PC and Installing or un-installing apps to device
Any tips or step by step how should do to install Bionix 1.3.1 with kernel Tigers Blood with Voodoo sound and colors without a problem?
or maybe to install Axura with out been so lagging.
Any reason for not testing Trigger, with OverStock 2.2?
Try trigger, or a 2.2.1 port. Pne of those may work faster.
Sent from my GT-i9000/Vibrant.
s15274n said:
Any reason for not testing Trigger, with OverStock 2.2?
Click to expand...
Click to collapse
I will try this mate and report back. I just did an back up and now lets just see how this setup does it for me. All I want is a good theme ROM, fast and stable, Honestly I loved the Axura ROM but is to lagging for me for some reason.
Bionix is great but I have the same problem with all the roms I install. When the USB is not detected then is the apps cant be install or un-install.
Will try this one as I havent yet and besides it gives me more experience nothing to loose.
Thanks mate
Feel free to shoot me a pm if needed. Just be sure you've read the noob guide.
s15274n said:
Feel free to shoot me a pm if needed. Just be sure you've read the noob guide.
Click to expand...
Click to collapse
OMG here we go again, I think Im doing something wrong. I have the same issue as the more same I do like the How to's state I have the problem with installing and un-installing soft. When i even try to restore my back up for apps from Titanium it wont let me since all the apps stay like computing. I think is something wrong with the apps system or something.
I havent flashed yet the kernel.
I will try to install the ROM again
Not to sound rude, but did you follow the instructions in the noob guide on the proper way to backup, flash and restore?
Perhaps you should just ODIN back to stock and start over if you have.
Let me know if I can help, try and be detailed in your posts though... that last one, I really have no clue what you were trying to say.
Odin root cwm flash...... I hope your only flashing one thing at a time... Not rom+kernel+theme+ boot animation or somthing wildly stupid
Sent from my SGH-T959 using XDA Premium App
s15274n said:
Not to sound rude, but did you follow the instructions in the noob guide on the proper way to backup, flash and restore?
Perhaps you should just ODIN back to stock and start over if you have.
Let me know if I can help, try and be detailed in your posts though... that last one, I really have no clue what you were trying to say.
Click to expand...
Click to collapse
I really love this ROM looks great and very smooth. I will use ODIN and go back to stock then I will root and then will flash with CWM and comeback here for some tips. I want to get this right for the first time at least.
TY so much mate
Ok, Im done, I have installed the ROM and let it sit for 10 mins at least then rebooted. What step should I do now to flash a kernel like Tiger blood or OverStock.
Or what will be the next step other then configuring the login for google?
nate420 said:
Odin root cwm flash...... I hope your only flashing one thing at a time... Not rom+kernel+theme+ boot animation or somthing wildly stupid
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
I did used the ODIN to Stock Flash my phone and then one out a time after reboot ect...
you may want to stay stock trigger for awhile and test it out.
when ready, download overstock 2.2, move it to sdcard/, reboot to CWR, install from zip (like a rom), after you flash it, reboot.... you'll notice a new splash screen for overstock, all done.
s15274n said:
you may want to stay stock trigger for awhile and test it out.
when ready, download overstock 2.2, move it to sdcard/, reboot to CWR, install from zip (like a rom), after you flash it, reboot.... you'll notice a new splash screen for overstock, all done.
Click to expand...
Click to collapse
Ok, I have seen enough of this. lol I so sad to see how easy this is but frustrated when I get problems like the one I still have. Everything was great until I started installing the apps from the Titanium back up i made. It did installed about 15 apps but after those been installed successfully it just got stocked loading and it wont install any more apps or even un-install. Cant even install apps from the market.
What is wrong with this thing, is very stressful try and try and get the same result on 4 different ROMS I have tested already. I really hate to ask for help as I like to read and try it for myself so I can about a new hobby.
But this one is biting my hand very hard. Can you please tell me ehat can I do in this case mate to trouble shoot this?
Thank you for your time friend
Something I have done a bit different is that I have put the files in separate folders for more organize.
Like for sample; at sd_root/ I have a folder name Download which it have sub-folders that look like this tree below
Download
//
-Kernels/
-Metamorhp Mods/
-Misc Mods/Apps
-Modems
-Mods
-Roms
-Themes
Do you think that will be a problem by not having the Files at the root location at SD?
When you are restoring your titanium back ups, are you only restoring apps? I mean, are you restoring system data too? You don't want to restore system data, and only restore apps. Sometimes restoring system data from previous roms can cause problems.
If this still doesn't help, you might just want to redownload all your apps, and then make a backup. Sounds like your issue is linked to titanium back up.
Sent from my SGH-T959 using XDA App
dougstoner said:
When you are restoring your titanium back ups, are you only restoring apps? I mean, are you restoring system data too? You don't want to restore system data, and only restore apps. Sometimes restoring system data from previous roms can cause problems.
If this still doesn't help, you might just want to redownload all your apps, and then make a backup. Sounds like your issue is linked to titanium back up.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That makes sence!! I will load the ROM again and start over and see how it goes installing just the apps. I was restoring the apps and data
If it doenst help I will continue your suggestion to install the apps one by one NOT from the Titanium as it was back up from a different ROM.
thanks i will let know how it goes.
stay away from restoring system data when flashing roms. Just the apps with the app data. Hope this helps man. If not, let's go over the entire order of what you are doing and we will figure out what is going on.
Sent from my SGH-T959 using XDA App
Ok here goes to nothing. I have dont everything correctly like the Guide's stating and everything works great at first but them it just stop working the whole file system apparently. Is just works great and after few app installs it just fail. When I go to check the files from the File management it just say Computing instead of loading and give the file size info ect....
What can it be I dont have a clue as I have search the whole forum and I dont see this problem posted by any other. Its just wont install, un-install or even cant stop any app from working.
What else can i do?
When backing up with Titanium, its okay to back up user apps and their data. As far as system data, Titanium has it sorted by what is and isn't safe to restore. Green entries are all good, don't back up any entries with red text.
This is how I've been backing up stuff since before 2.2 dropped, and I've never run into any strange issues.
Just a shot in the dark, but it might be a bad sd card, or just needing a format. Try backing up all your sd files on your computer, and format your sd card and see if that helps. I had some funky stuff going on with my phone, and it went away after I did that.
Hey Guys, I want to ask whats the reason for bootloops. I'm sick of them, I get them too often now.
I change themes sometimes, and suddenly all I'm left is bootloop. I change screen-lock type and again bootloops.
What my idea is, One can go into CWM recovery, mount the system and push/over-write some files through ADB & restore bootloop-free OS. What I don't know is list of files which can be reason for these bootloops.
Rushyang said:
Hey Guys, I want to ask whats the reason for bootloops. I'm sick of them, I get them too often now.
I change themes sometimes, and suddenly all I'm left is bootloop. I change screen-lock type and again bootloops.
What my idea is, One can go into CWM recovery, mount the system and push/over-write some files through ADB & restore bootloop-free OS. What I don't know is list of files which can be reason for these bootloops.
Click to expand...
Click to collapse
If you mean reboots FAT has them, switched back to vo-1 CM build 17.02.2012 (best and fastest ROM ive used!)
http://forum.xda-developers.com/showthread.php?t=1360889
tomsons26 said:
If you mean reboots FAT has them, switched back to vo-1 CM build 17.02.2012 (best and fastest ROM ive used!)
http://forum.xda-developers.com/showthread.php?t=1360889
Click to expand...
Click to collapse
No. I'm talking in general. I also had these problems with other ROMs. Lucky I always had CWM Backup ready to restore them. But no-one is free enough to take CWM backup daily. So it's better to have solution of it I think.
Rushyang said:
No. I'm talking in general. I also had these problems with other ROMs. Lucky I always had CWM Backup ready to restore them. But no-one is free enough to take CWM backup daily. So it's better to have solution of it I think.
Click to expand...
Click to collapse
I also had these problems with other ROM.
Click to expand...
Click to collapse
Then its not a ROM problem is it?!
Make a backup
Try flashing newer official samsung firmware and then restore backup.
Doing this will update modem and some suff in the phone that a ROM can't
The only way is running on the bootloop adb logcat and look on the log what crashes the system. For my I made a SMS backup every day, and CWM backup one in the week and deleted the old backups.
every file in system partition can cause bootloop. Even a single line in build.prop can cause bootloop.
Sent from your phone
tomsons26 said:
Then its not a ROM problem is it?!
Make a backup
Try flashing newer official samsung firmware and then restore backup.
Doing this will update modem and some suff in the phone that a ROM can't
Click to expand...
Click to collapse
But I have never changed modem and other kernel. I'm not on custom kernel either. All I have done till date is, rooted my SGA and flashed custom ROMs. That's it. So I don't think modem or other stuffs might be the problem here.
dragonnn said:
The only way is running on the bootloop adb logcat and look on the log what crashes the system. For my I made a SMS backup every day, and CWM backup one in the week and deleted the old backups.
Click to expand...
Click to collapse
So, do you mean that when my SGA is on bootloop, I can connect with ADB logcat and check at the same time what causes the problem? That sounds interesting.
an0nym0us_ said:
every file in system partition can cause bootloop. Even a single line in build.prop can cause bootloop.
Sent from your phone
Click to expand...
Click to collapse
When you apply the new theme through "Theme Change" engine in CM7. Which files are altered?
Rushyang said:
But I have never changed modem and other kernel. I'm not on custom kernel either. All I have done till date is, rooted my SGA and flashed custom ROMs. That's it. So I don't think modem or other stuffs might be the problem here.
So, do you mean that when my SGA is on bootloop, I can connect with ADB logcat and check at the same time what causes the problem? That sounds interesting.
When you apply the new theme through "Theme Change" engine in CM7. Which files are altered?
Click to expand...
Click to collapse
It depends on the theme.....how it themes...
Sent from my GT-S5830 using XDA App
Prawesome said:
It depends on the theme.....how it themes...
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Guys, cut to the chase already! Let's consider the normal theme "System" or "Androidian". & Then go to the most changes applying them "UOT Kitchen".
No one, "actually" know or caring to share?
Anyway, let me tell you what happened just now, I changed "LockScreen Wallpaper" from CyanogenMod Settings and boooom! Bootloop. Restoring Nandroid back up now.
Is there anyway to know which files are being changed when I did that?
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
i've used this phone almost 1 year with no problems for cyanogen mod 7.1.0
when i play some apps general i've notice a bit slow running like exactly if you have a pc old that run pretty slow for playing game.
This never happened when i buy first time but now i have this problems from a fews days ago i also didnt installed others apps untyl now so i have no idea where exactly come out this problem.
Thought i have too much apps around 99 apps so i've take decision to format all on sdcard and data, cache and wipe data factory reset (i've also flash from 7.1 to 7.2 cyanogen) and wipe dalvik. Like everyone do usually....
At the end when is empty all apps i tried to install JUST one game and still got same problem.....its running SLOW sometime but i dunno why.
Someone can explain me why do this strange behavior? is a problem hardware? i dont think is something to do on software or programs apps issue.
this make me nervous now...
Can you try installing a different ROM?
votinh said:
Can you try installing a different ROM?
Click to expand...
Click to collapse
Ok but doesnt make sense if before was working fine with version 7.1 almost 1 year (i tried reinstall 7.1 but is same problem) so why having problems now? i dont have nothing on phone right now is pretty clean cause of formatting at all...
So come to think this phone is not normal...
Format your /data /system /cache and /dalvik. Then flash whatever rom u want. I would suggest first downloading the newest cm7 or cm9. But u could stick with what u had if u Want.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Phalanx7621 said:
Format your /data /system /cache and /dalvik. Then flash whatever rom u want. I would suggest first downloading the newest cm7 or cm9. But u could stick with what u had if u Want.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Yeah i did already exactly what u say formating data + system + cache and davilk yes and also i tried to download last version for cm7. (that why i say 7.2 instead 7.1 now after all is last version already..)
EDIT= i did format too sdcard definitly complet i guess and result? nothing
No is not possible! I tried to flash now for last cyanogen mod 9 nighty and still SAME PROBLEM AGAIN.
Help i cant do nothing?? I tried many alternative but im out of idea now -.- so sad...
Really not sure what the problem is but I just wanted to suggest that you return to stock via Odin and see if you are still experiencing the slowdown.
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