Develop Bugs

[HELP] Problem with flashing Myn’s Warm TwoPointTwo RLS 5

Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..

tobiasunruh said:
Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..
Click to expand...
Click to collapse
You did a full wipe prior to flashing right? Maybe try re-wiping everything, then flashing the rom again.

Do you mean a all user data/factory reset? If so then no. I wiped data, cache & dalvik tho. I also tried three different sources for the rom download and flashed all three and got the same results each time.

When you flash a new rom, you should always wipe EVERYTHING: cache, data, factory reset, and dalvik. Try doing it again with wiping all of this first.

tobiasunruh said:
Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..
Click to expand...
Click to collapse
Your EVO needs a WIPE!! I prefer to use C's Format All Zip TWICE as well as separately wipe Cache and Dalvik TWICE. After first boot, I like to reboot to recovery and wipe the Dalvik two more times. Reboot, fix permissions, reboot and you should be good to go.

Thanks guys.. I will try that right now and let you know how it turns out..
Can any one tell me where to find the cs format?
And do I need to format my sd card?
Sent from my PC36100 using XDA App

tobiasunruh said:
Thanks guys.. I will try that right now and let you know how it turns out..
Can any one tell me where to find the cs format?
And do I need to format my sd card?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hey man. Attatched is a copy of Calkulin's Format all. You flash it in recovery, and it wipes everything. It ensures a solid wipe. Use your recovery to wipe data/factory reset, cache, and davlik cache two times each. Then flash this zip in recovery. Then reflash the ROM. That should do the trick for you, Myn's runs good and clean!
Edit: And no, you do not need to format your SD card.

I wanna say thanks to all you guys for your help. I have it installed and running great.
If any of you have any recommendations for mods I'm open to suggestions..

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick

What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed

Try a full wipe, cache, dalvik, and data. Then reflash the rom.

By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?

That's correct, just wipe dalvik and cache before doing so.

So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...

I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17

You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.

The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??

deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.

Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.

deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.

No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?

Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.

Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.

deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

[Q] Flashing from CM7 nightlies to a different ROM?

Hi everybody....Ive been flashing ROMs from ROM Manager and never had problems...until I tried to flash from CM7 nightlies #66 to a leaked G2 ROM][04/28/11] TMOUS G2 Gingerbread 2.13.531.5.
I did the usual wipe cache and dalvik and proceeded, it seemed like it was downloaded but got stuck on the reboot, it was stuck on the HTC logo for a long time. I thought I bricked it but managed to get it to work by taking the batterie out and going into recovery by clockworkmod.
Is there any special way to flash ROMs from the nightlies on a G2?

You said you wiped cache and dalvik, but did you wipe data too(factory reset)? Pretty sure you need to do that if coming from cm to the stock tmo leak. Could be wrong but sounds about right
Sent from my T-Mobile G2 using XDA Premium App

that is right anytime change roms that are not linear to the same dev, it is best to wipe all, data/factory/cache then flash rom

ilostchild said:
that is right anytime change roms that are not linear to the same dev, it is best to wipe all, data/factory/cache then flash rom
Click to expand...
Click to collapse
Hmm, I checked everything that ROM Manager suggested, cache/ dalvik, the only thing I didnt check is to back up current ROM.
If you wanna wipe all that data/factory/cache do yo have to flash it manually?

Flashing other roms I think messed up my phone lol. I just stay with cm7 now lol
Nonsense!

ms9007 said:
Hmm, I checked everything that ROM Manager suggested, cache/ dalvik, the only thing I didnt check is to back up current ROM.
If you wanna wipe all that data/factory/cache do yo have to flash it manually?
Click to expand...
Click to collapse
even if you did say to wipe /system and /data in addition to /cache, CWM is notorious for not actually formatting the partition. go into the dev section and find SuperwipeG2 and if you are switching from aosp<->sense or, as earlier mentioned, from one dev's rom to another, run superwipe before doing so.

Halp, I'm unable to flash new roms...

About a month ago I went from myns 2.2 to CM7 and eventually cm7.1 well I had terriable 3g 4g wifi and gps connection issues with CM and I flashed a bunch of kerenel and radio driver combos trying to fix the problem. Well out comes the synergy and I decide to try that and give up on CM. I did the usual wipe dalvic data ect twice and flashed synergy which got stuck on the white evo splash screen and won't go past that. Additionally when I flash any other rom's either myn's, cm, ect I get the same problem. I have tried wiping several times with both the Clockwork and RA recoveries with no success. As it stands now I can only recover previous nandroid backups or run the pc186img. Anyone have any ideas??? Help would be appreciated.
Thanks
Frankie

Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.

Frankie_Bones said:
or run the pc186img.
Frankie
Click to expand...
Click to collapse
hope thats an typo

dased14 said:
hope thats an typo
Click to expand...
Click to collapse
yeah pc36img

teh roxxorz said:
Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.
Click to expand...
Click to collapse
Worked, thanks. I had myself worried for a minute there.

[Q] boot loop

I flashed CM7.1 and I'm stuck in a boot loop. I tried wipe cache partition, wipe date/factory reset, wiping dalvik cache and reflashing a different rom but still keep getting the boot loop. What else should I try doing to slove this ?

Could be kernel related, are you using an aosp and hopefully not a sense kernel? Need more info, what kernel, recovery are you using?

I'm using ClockworkMod recovery I'm not sure what kernel I using

Easy fix, recommend starting from new. wipe the entire phone in recovery at least 3 times, sd card also, backup sd card to computer if you need to via USb toggle, flash Cm 7.1, flash tiamat kernel, found in development section, reboot, good to go, nandroid once up and running, happy flashing

Thanks, okay I'm glad you said easy fix I'm not as worried now. I'm gonna follow your advice. Whats a roamer kernel ?

sorry swype acting weird, use tiamat kernel 4.1 something in development section

The FIRST Thing you should do is get rid of Clockwork Mod, and get Amon Ra, so you can wipe everything.
Just wiping Data/Cache/Dalvik when flashing a new ROM isn't enough.

Hey thanks again ! ! I followed your advice and got everything working again