Okay, I'm here everyday reading this stuff, Id first like to say you guys rock. Everyone here, and the makers of these awesome mods, you have made my phone and my life quit amazing, and less boring like stock!
It seems something is wrong
I sort of switch back and forth between cm and savage zen when each have an update. I love savage zen because of the higher resolution, makes my evo screen crystal clear, while cm is much more stable, and has not only the meat, but the potatoes and gravy, while savage only has the meat
But anyway, no matter what I do, gmail crashes, and media crashes, market doesn't work etc. The google apps in rom manager have worked before, when I was using 2.3.4 I was able to find that google app package somewhere online.
The google apps in rom manager that im thinking of says its compatible with 2.3.3, and well I used it for a few weeks perfectly. Silly me though I'm never satisfied...
I'm running 7.0.3.1, but it seems the google apps that comes with that package has never worked, you know when you check the box for google apps.
So instead I would do it manually, and again I mean it worked fine.
I decided to go back to savage zen, loved it (everytime deleting delvik cache and full wipe)
I think I am missing something...
The order I would do things is, wipe dalvik cache/data, install mod/google apps. I mean that has always worked before just fine. I tried a before and after also, booted it before restoring my data, nothing crashed, it all went smoothly.
In recovery, I go to restore, advanced restore, then restore data. My 2 latest backups both fail. Am I not restoring correctly, oh im sure this is all my fault.
Sorry im sure this has been answered many times over...I found a few threads but they wernt quite what I was looking for because the person I was reading about both times was using cm6, and I think I did the steps correctly..but thats what I'm here for, Please help me fix my bad *** phone.
Quick Update
Okay, so yeah I do still have more to learn. I was thinking well maybe if I just wipe the cache partition....(havnt done that before..just did full wipes)
Is this all my fault? Maybe all this going back and forth is just not good? lol
I figured this out by myself. I went into titanium backup, and wiped the cache of every program that was giving me the error. Done and done. I guess clockwork mod doesn't get rid of all cache?
Well..thanks anyway...I didn't find the fix on google, or anywhere for that matter..It just came to me..
I remember reading comments about how clockwork dosent nandroid wimax keys and does not fully wipe like it should, you should try switching to amon's RA recovery.
I switched to Amon Ra a few months ago. I agree it's way better and it's nice to be able to whipe dalvik cache without waiting a few minutes for it to even get to the right screen, but I have still had a few problems even after dalvik/cache wipe. Titanium backup is a nice way of cleaning things up also, media storage!
That's something I figured out, it was media that kept crashing and it's happened again, but I do flash like a junkie! Always making sure to wipe dalvik/cache and making a nandroid backup before flashing.
Going into settings, applications, media storage then clear data. Works like a charm.
Also once I had 2 ringtones playing when my phone rang...couldn't figure it out and did EVERYTHING. Clearing media storage saved the day.
I think I'm done flashing..may of found my perfect combo
Synergy rls1 + godmode with aggressive freedom kernal.
mmmmm delicious! RLS1 made the phone actually seem to be overclocked before overclocking it (If that makes sense LOL), it ran just as smooth as it did running cyanogen overclocked to 1190. Of course I overclocked it anyway
Related
But I'm having random freezes/crashes, especially when I watch an embedded youtube vid.
What's the best way to troubleshoot?
TIA,
Tx
Tx Redneck said:
But I'm having random freezes/crashes, especially when I watch an embedded youtube vid.
What's the best way to troubleshoot?
TIA,
Tx
Click to expand...
Click to collapse
Make sure when you flashed from the stock rom, you wiped data, wiped cache, and wiped dalvik cache. If not, do it and reinstall.
I didn't do that because I was afraid to loose apps that I already had and didn't know how to recover stuff once the flash is done.
try MyBackup Root
i'm about to find out how well it preforms after wiping and installing a new rom. i'll let you know.
so i went from liberated froyo fr008 to cm6-6.1.1 and it appears to have restored all my apps + data + settings as best it could considering its a little different from the sense system.
apps work, settings work. the app worked =D
I would like to have a clean install(see no ATT bloat) but not have to go through and configure everything. What's gonna be the most stable Rom?
Tx Redneck said:
I would like to have a clean install(see no ATT bloat) but not have to go through and configure everything. What's gonna be the most stable Rom?
Click to expand...
Click to collapse
Based on your original post, since you are rooted and running FR008, then you already have a very stable ROM with HTC Sense and does not have any AT&T bloat on it.
It looks like the mistake you made as far as stability goes is that you did not perform a Wipe Data/Factory Reset before you flashed FR008 in hopes of keeping your apps and settings. I suggest you bit the bullet and do a Wipe Data/Factory Reset and then reinstall your apps and you'll have a very STABLE environment.
Lemme ask this, right after rooting and running nandroid, I pulled the the sd card and copied its entire contents(at east as much as Win would "see", not sure about any additional partitions) to my lappy.
If I do a clean install by wiping all factory data, cache partition and dalvik, will I be able to restore any items from that copy I made?
Please forgive me for teh newb questions. I can fix a puter all day long, this android stuff is greek to me.
Tx Redneck said:
Lemme ask this, right after rooting and running nandroid, I pulled the the sd card and copied its entire contents(at east as much as Win would "see", not sure about any additional partitions) to my lappy.
If I do a clean install by wiping all factory data, cache partition and dalvik, will I be able to restore any items from that copy I made?
Please forgive me for teh newb questions. I can fix a puter all day long, this android stuff is greek to me.
Click to expand...
Click to collapse
If you did a nandroid backup to your SD card, yes nandroid has an advanced restore option where you can selectively restore different partitions from the backup, such as boot, system, data, cache, etc. although I have never tried it.
Rooted last night with the Liberated FR008 rom and everything seemed to go smoothly, now though my browsers won't stay open. If I try to go from a link in an email the browser will open then close, pretty much same thing when I just open the browser. Any ideas why this is happening?
Phone: HTC Aria
Browsers tried: Default, Dolphin HD, xScope
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.
mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.
I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App
Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.
Cool glad you got her going.
Kaaameeehameeehaaaaaa!
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
Click to expand...
Click to collapse
Are you using ROMs that have Google back up enabled?
Also, if the zip isn't set to wipe /data and you're not wiping it then you'll still have all of your data.
That has happened to me too. Are you wiping sdext and android.secure in recovery. I always wipe those and haven't had that happen since I started doing that.
We're comin from a pure power source.
naw i turn off all that google backup stuff.
thats the thing, when i try to wipe sdext it gives me an error (from the last i remember doing it)
Hmmm. Latest version of amon ra?
We're comin from a pure power source.
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You should be wiping data as well when flashing new roms.
I flash vrsuperwipe everytime I flash, but I use Google backup, so when I flash a new sense ROM it saves a lot of my settings, and my SD-ext apps automatically appear. Good feature imo.
Sent from my PC36100 using Tapatalk
bump for any other answers or advice
thanks guise.
still wondering about other options before testing some new roms
same thing happened to me so I tried repairing sdext and then re-partitioned my card and left it ext2 instead of ext3,wipe data/cache/dalvik cache/system flash superwipe, then flashed rom. don't know which one worked but it stopped. Also I noticed it mainly happens when I flash 3.0 roms but it has happened on CM7 to
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You did not wipe data. If you do this you will preserve all of you apps (if they were not on card), data and system settings. This may work for you if the new ROM that you are moving to is similar enough. It can cause big problems if the structure of the ROMs is too different. You can end up with a phone that lags and has wakelocks (at best) or is not functional at all due force closes all over the place.
You should really wipe data as well before flashing a ROM and then do a selective restore of data on the new ROM.
I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...
After updating to 3.01 ...occassionally my power button does not turn screen on, keyboard lights up, but screen will not come on...have to pull battery...anyone else??
No problems here. That kernel is kickin ass on my phone. A clean install, wipe cache dalvik and data, will alleviate 99% of those quirky problems.
Backup your apps and data thru titanium backup
Go to cwm
wipe cache
wipe dalvik
wipe data
Install ROM
Install kernel
if your installing a theme, wipe cache and dalvik again, probably not necessary, but it won't hurt, then install theme.
Reboot system
Go on the market, and get your apps, especially Titanium Backup.
Try to restore your apps back thru Market rather than titanium, this ensures that your apps are not corrupt in some way. If there are certain apps that for one reason or another are no longer available from Market but you absolutely gotta have it. Restore it from titanium.
Restore data from Titanium, but only whats absolutely necessary.
Sometimes things get corrupted when flashing over and over and the above method works everytime to get it back solid and glitch free.
Restore only the data
Xalky said:
No problems here. That kernel is kickin ass on my phone. A clean install, wipe cache dalvik and data, will alleviate 99% of those quirky problems.
Backup your apps and data thru titanium backup
Go to cwm
wipe cache
wipe dalvik
wipe data
Install ROM
Install kernel
if your installing a theme, wipe cache and dalvik again, probably not necessary, but it won't hurt, then install theme.
Reboot system
Go on the market, and get your apps, especially Titanium Backup.
Try to restore your apps back thru Market rather than titanium, this ensures that your apps are not corrupt in some way. If there are certain apps that for one reason or another are no longer available from Market but you absolutely gotta have it. Restore it from titanium.
Restore data from Titanium, but only whats absolutely necessary.
Sometimes things get corrupted when flashing over and over and the above method works everytime to get it back solid and glitch free.
Restore only the data
Click to expand...
Click to collapse
Thanks,
Should have provided more pre-info...did the wipe davlik and cache thing as normal. Have moved between the voodoo and samurai kernel and OP problem is the first I have encountered. Thinking about going backl to Sam 2.08...no problems there. thanks again for the speedy help!
Yep,
3.01 is amiss ...went back to 2.08 and all is fine now... on the development forum it looks like other users of 3.01 are experiencing the same problem...
Naddict said:
Yep,
3.01 is amiss ...went back to 2.08 and all is fine now... on the development forum it looks like other users of 3.01 are experiencing the same problem...
Click to expand...
Click to collapse
I am using Samurai 2.0.8 as well with absolutely NO problems
The screen not coming on is a wakelock.... your cpu doesn't like the 100mhz step which means you need to get that unchecked in voltage control unselecting it that should fix the wakelock...maybe ^^
Sent from my OG Epic
Thanks Biggoron, I saw a post about that issue somehwere and I turned off the 100mhz step in voltage control...still had the issue and, as I mentioned earlier, am seeing other users still having the problem with all three 72mhz versions....interesting....I have always been a lurker and never contributed...so now I am working on my 10 posts just so I can at least offer my observations. Thanks again
Figured it wouldn't of changed anything thus the ....maybe^^
Hopefully earthbound will figure out the issue have you tried any of the 60hz versions to see if it still occurs?
Sent from my OG Epic
No,
I went back to the Voodoo kernel (1.01oc/uv), it has been pretty stable, and so was Samurai 2.08....
No problems with 2.08 or 3.01 power button, even running at 100 mhz. However, my rotation lag came back not sure if it's the rom (Marcusant's v1) or the kernel, or something else... it seems the only issue so have to live with it.
for what iti is worth, I also noticed a little "lag" or interuption in my notification sounds with 3.01...but that is all behind me now. sticking with voodoo 1.01 for now. seems to be the most stable other that nube's...anyone know when he is putting up a new kernel?