i find that the nightly build is cool and is awesome. the problem is when i use system panel task manager, the phone reboots. i dont know why and its more laggy than the cm7 mod please tell me its me doing something wrong not my phone's or the mod's fault.
and it svery irritating that it keeps hanging. please someone help me with the nightly mod thing i want to use.
Go for nightly#205. And do a full wipe including data,cache,dalvic cache, and perform a factory resetting from cwm before you flash the nightly. Also use latest buzz kernal so that you can overclock your phone.
Sent from my HTC Wildfire using XDA App
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
ongtengjun said:
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
Click to expand...
Click to collapse
i had problem with my previous nightly # 177 when i used darktremor APP2SD script .. even when i re flashed nightly #205 .. things were the same (Talking about random reboots upon opening task manager / and installing apps etc. ) ..
then i repartitioned my SD and didn't flashed the script... now its fine .. ..
so how did you install it? how to repartition sd card and not flash the script? how to install?
V0odo0 said:
i had problem with my previous nightly # 177 when i used darktremor APP2SD script .. even when i re flashed nightly #205 .. things were the same (Talking about random reboots upon opening task manager / and installing apps etc. ) ..
then i repartitioned my SD and didn't flashed the script... now its fine .. ..
Click to expand...
Click to collapse
Lol you may have used beta 4 script, try beta 3, need to use atleast ext3 as your secondary partition. Try it with latest original cwm recovery. 5.xxx to partition. Do a clean install after partition.
And a personal suggestion. S2e app in market is good than dta2sd, though it have not much functions, but what it have, it does its best. I use it.
Sent from my HTC Wildfire using XDA App
ongtengjun said:
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
Click to expand...
Click to collapse
Dude, explore options in cwm, don't do formatting boot, system, data, unless you learn what it does.
Options may vary from version to versions of cwm. So you have to say which cwm version you have. Mine is latest 5.xxx.
In it, data- factory format( user data or wipe user data, which ever it is called) is in main menu. And dalvic cache wipe is in advanced menu.
Lol you must carefully read topic named" complete wildfire index, then ask doubts, after all you can learn new things from every topic.
Your kernal will be in that topic. Check it out.
Sent from my HTC Wildfire using XDA App
another problem
now i got another problem. my wildfire will hang every now and then and i have to pluck out the battery and switch it back on. its very irritating and having to keep doing that will kill my bat very quickly so could anyone tell me any solutions?
To solve your problem, you must say. Your current configuration, rom, kernal, radio, tweeks, and what have you done just before you got the error
Sent from my HTC Wildfire using XDA App
well i am using the cm7 nightly build #205. kernel is buzz-kernel-2.6.35. i just downloaded some apps that were in my phone when i was using cm7 stable. and there wasnt a problem. do i have to upgrade to latest build and kernel? oh and just a question. if i want to upgrade from #205 to #208, do i have have to like wipe my data and cache and dalvik cache? i wouldnt wanna redownload and change everythin again
You can install the nightlies on top of one another without wiping anything, sometimes it seems better to wipe the cache to me but not always necessary, leave data alone.
Word of warning though, always make a nandroid backup before installing a new rom, although they're stable they are still called experimental for a reason, and sometimes (not very often) things can still go wrong.
Sent from my HTC Wildfire using xda premium
i wiped both the dalvik and partition cache and installed the #208 nightly build and the latest kernel but then the phone would just restart automatically. do i have to wipe data as well?
Yes do a "Wipe Data / Factory Reset" in Clockworkmod if it is giving you issues. Then try a fresh install and check again for instability.
Note - Performing a Wipe Data / Factory Reset will erase all data (Except SD Card)
well i not sure but i think the problem still occurs.. yes it does. i wiped data, cache and dalvik cache, did a install using cwm and it still reboots WHAT TO DO NOW
showlyshah said:
Lol you may have used beta 4 script, try beta 3, need to use atleast ext3 as your secondary partition. Try it with latest original cwm recovery. 5.xxx to partition. Do a clean install after partition.
And a personal suggestion. S2e app in market is good than dta2sd, though it have not much functions, but what it have, it does its best. I use it.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Hey thanks dude .. yup i was using beta 3 last time.. beta 4 was a disaster to CM7.. .. i tried that too ..
but i think my partition was ext2 coz i am using CWM 3 .. will try with CWM 5 .. and sure... S2e too ...
Do you let it boot up before flashing the kernel?
Sent from my HTC Wildfire using xda premium
For i always keep a backup of my contacts in sd. Also apps using titanium backup, i had never used a nandroid backup till now, i alwayz do fresh installs, wiping every thing but not fat32. And always keep things updated.
Sent from my HTC Wildfire using XDA App
ok now i have another problem. my phone will just reboot after hanging when i open system panel task manager. please some one help me
ongtengjun said:
ok now i have another problem. my phone will just reboot after hanging when i open system panel task manager. please some one help me
Click to expand...
Click to collapse
dude is it the same one you had before? thats why we mention to give your current spec. with out it we cant do any thing or we cant help you.
Related
I just installed a new kernel and afterwards read about clearing the dalvik cache before installing kernels. Since I never did this should I clear it now, or do I have to clear it and then install the kernel?
clear then install
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
jprow507 said:
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
Click to expand...
Click to collapse
To be on the safe side i do it both in Titanium and then when i am in Clockworkmod, I do it in the advanced section too - by the way if you do not have partition done on your sd card u will see an E: error message. You can ignore that.
khanam said:
To be on the safe side i do it both in Titanium and then when i am in Clockworkmod, I do it in the advanced section too - by the way if you do not have partition done on your sd card u will see an E: error message. You can ignore that.
Click to expand...
Click to collapse
Thanks alot .... I did it the way you suggested and am rebooting now. I appreciate the help.
For kernels, you want to delete the cache partition, kernel stuff usually isn't help in the dalvik cache. On Amon_Ra style, it's wipe cache. On CWM I think it's wipe cache partition (Don't know, have not used CWM in a while).
jprow507 said:
Is this the same thing as "cleaning" the dalvik cache using Titanium or do you actually have to delete the entire cache folder?
Click to expand...
Click to collapse
Cleaning in Ti only deletes unneeded files. Do this after you uninstall an app or two. Wiping in Recovery clears it out completely, so you'll have a longer next boot time while it's rebuilt. You only need to wipe it when changing to and from one of King's with HAVS.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Cleaning in Ti only deletes unneeded files. Do this after you uninstall an app or two. Wiping in Recovery clears it out completely, so you'll have a longer next boot time while it's rebuilt. You only need to wipe it when changing to and from one of King's with HAVS.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
So I don't need to wipe when updating Chads incredikernel?
You should always wipe caches when swapping kernels, even it its switching kernels from the same dev. It takes like no time to do so why not? I've forgotten to and usually it makes no difference. Sometimes its just forced closed's until I can restart and do it right.
Sent from my ADR6300 using XDA App
loonatik78 said:
You should always wipe caches when swapping kernels, even it its switching kernels from the same dev. It takes like no time to do so why not? I've forgotten to and usually it makes no difference. Sometimes its just forced closed's until I can restart and do it right.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
that would be very TROLOLOLOL
Hi guys I own a htc desire 526GPLUS with mediatek 6592 and the manufacturer doesn't released source codes
Now I want to port a rom made for another device with mt6592
Can I port it and can I use drivers by copying it from driver folder from my stock rom and I will use boot. Img from stock rom
Question 2
What makes different devices require different kernels?
If I get mt6592 source code from another device can I make it to work with mine
Please help
Hi all
The htc white screen and repeating quite brilliant pissed me off after installing new rom ,i cant install any rom i tested 6 or 7 rom its already give me this error.
How to do?
Whats this problem plz?
Sent from my HTC Desire using XDA App
Do a full wipe before flashing.
Sent from my HTC Desire using XDA Premium App
TheGhost1233 said:
Do a full wipe before flashing.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
i did and it doesn't work .
thanks
Any one have other solution please???
Sent from my HTC Desire using XDA App
Have u factory reset cleared cache and also cleared dalvik?
Sent from my Desire HD using XDA App
Alright..
Firstly, reboot into recovery and wipe full data & the dalvik cache.
Second, flash a rom to which your device fulfills all requirements (eg. not D2EXT, D++)
Third, restart your device after installing the ROM.
Fourth, WAIT!!!!! if it doesnt boot after like 15 minutes then something has gone wrong somewhere.
Just to make things easy to start with, you should try using a rom that doesn't require an ext2/3/4 partition and just uses fat. Unless you are confident you can do that correctly.
Aegishua said:
Alright..
Firstly, reboot into recovery and wipe full data & the dalvik cache.
Second, flash a rom to which your device fulfills all requirements (eg. not D2EXT, D++)
Third, restart your device after installing the ROM.
Fourth, WAIT!!!!! if it doesnt boot after like 15 minutes then something has gone wrong somewhere.
Just to make things easy to start with, you should try using a rom that doesn't require an ext2/3/4 partition and just uses fat. Unless you are confident you can do that correctly.
Click to expand...
Click to collapse
its impossible, all owners of desire do that?
all roms was created to work with Desire !!
snowwhite007 said:
Have u factory reset cleared cache and also cleared dalvik?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
how to clear dalvik?
thanks all ,after wipe partition and wipe data factory , worked with me.
this wipe partion deleted my ext partition also?
thanks
Seriously, you should do a little reading tutirials and guides on flashing.
You cannot flash a ROM with a different base on top of another - that's why the bootloops. (E.g. Flashing DHDport on top of Stock Rooted or GB on FROYO won't work without wiping).
Secondly, it is wiped it - ergo FORMATTED it, the ext partition is still there.
davebugyi said:
Seriously, you should do a little reading tutirials and guides on flashing.
You cannot flash a ROM with a different base on top of another - that's why the bootloops. (E.g. Flashing DHDport on top of Stock Rooted or GB on FROYO won't work without wiping).
Secondly, it is wiped it - ergo FORMATTED it, the ext partition is still there.
Click to expand...
Click to collapse
I understand that i have to see which radio can work with?
Sent from my HTC Desire using XDA App
Listen, everybody's here to help each other. It's what we android users do.
A little of "Please", and "thank you very much", "you guys are great"... goes a long way...
As for the radio, the easiest would have been, to upgrade your stock system to Froyo 2.29 before running the ROM.
Stock, before a custom ROM. This would probably avoid any radio problems.
If your phone is working and you have no issues, then you shouldn't worry about it.
Some people, get a little angry, when the same problem happens over and over again, and there are posts to cover these problems.
But, I think most of us, will jump right in, and give a hand to those who ask politely. And give a big thanks, when the issue is fixed.
Oh, and all ROMs are not created to work with Desire...
I flashed Sandvold's ICS 0.8.1 yesterday, but after reading a few threads today I saw that it's better to do the custom install instead of the typical one. I did a nandroid and decided to simply flash the rom again without clearing anything.
It seems fine so far, but I'm wondering if this can lead to any problems?
Also, do I need to reinstall a2sd after re-flashing?
I think that if you downgrade from ics to gb than you need to make a full wipe but if you upgrade than I think it's ok
Sent from my WT19i using xda premium
thedancingbear said:
I flashed Sandvold's ICS 0.8.1 yesterday, but after reading a few threads today I saw that it's better to do the custom install instead of the typical one. I did a nandroid and decided to simply flash the rom again without clearing anything.
It seems fine so far, but I'm wondering if this can lead to any problems?
Also, do I need to reinstall a2sd after re-flashing?
Click to expand...
Click to collapse
Yes, always wipe.
xdevilium said:
I think that if you downgrade from ics to gb than you need to make a full wipe but if you upgrade than I think it's ok
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
If you are with the exact same rom then a wipe shouldn't be needed and a2sd should stay if you don't wipe.
Try it and if it doesn't work do a full wipe I've never seen anyone say you'll break your phone if you don't wipe. Someone on Sandvold's thread recommended app extractor from play store as an easy way to restore after a full wipe. Didn't work for me but I only tried it once so you could check that out. It just restores everything from your nandroid
Sent from my HTC Desire using xda premium
greenie25 said:
If you are with the exact same rom then a wipe shouldn't be needed and a2sd should stay if you don't wipe.
Click to expand...
Click to collapse
If u are flashing the same rom (newer version) u still have to wipe dalvik. Its better anyway just to do a backup then full wipe and flash the rom then restore
Sent from my HTC Desire
Always wipe Dalvik, sometimes, the rom setup menu does it automaticly.
First off if you're on ANY recovery that isn't CWM 5.0.2.7 you DO NOT NEED TDJS SUPER WIPE OR CACHE WIPE SCRIPTS!!!! Seriously stop flashing these people you're filling up threads with problems caused by both of these scripts and bad flashing methods. Here's how to PROPERLY flash a ROM..
If on CWM 6.0.x.x
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
If you're on a Cyanogenmod nightly a full wipe IS NOT REQUIRED. The proper method of dirty flashing is just wiping cache, ( NOT FORMAT CACHE IN MOUNTS & STORAGE )
wiping dalvik and flashing your ROM. Simple as that.
If using TWRP 2.2+ the steps are essentially the same or use TDJs wipe scripts. They work perfectly fine with TWRP. Feel free to wipe 2x or even 3x if it makes you feel safer about your installation.
And THAT'S IT. People are cluttering up threads with issues than can totally be avoided by flashing the right way. I hope this helps some of you iron out these insane tiny quirks I keep reading about.
Happy flashing folks.
EDIT:
I forgot to note.. if you're still using one of TDJs roms or any other rom that automatically wipes with TDJs SUPER CACHE WIPE, do NOT use any other recoveries other than CWM 5.0.2.7 or TWRP 2.2+. With any other recovery such as CWM 6.0.x.x+, the wipe script breaks the roms ability to reboot properly and the only way to solve this is to use TDJs CACHE WIPE which in turn breaks your recoveries ability to work properly.
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks man this was needed. Yes threads get filled with this so often. I dirty flash like you mentioned accept I format system first. I also clean flash like you mentioned but never formatted cache and dalvik just system. That's good to know. Thanks
But I will add those new steps. I format system when dirty flashing because on the cm10 Site they mentioned that.
Again thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
I edited OP with a little bit more information for safer flashing.
Sent from my SGH-T989 using xda premium
Sad we need to keep telling people how to flash. If you are not sure what you are doing I think you should be very careful before you destroy your expensive toy. Everyone should have an idea on how to flash and restore from a bad flash before they even root. Also as my sig says let Google be your friend people if you run into issues instead of running to a thread and clogging it up...
Thanks for post and this is a bump to keep it on page 1 and hopefully more people will notice it.
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Goofy317 said:
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Click to expand...
Click to collapse
Can you boot into recovery at all? If you can.. download the TWRP 2.2.2.0 zip in its thread and flash it. Its going to hang in the install process but should say twrp has been installed. At that point reset your phone by holding the power button. As soon as you feel the phone vibrate hold down both volume buttons and you should boot into TWRP recovery.
Sent from my SAMSUNG-SGH-T989 using xda premium
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
Darkside superwipe will only mess your ROMs ability to reboot on touchwiz ROMs. The only way to fix this is flashing the darkside cache wipe which WILL break clockwork mod 6.0.1.4 like the user above. Point is.. don't use either scripts at all on CWM. Wipe the old fashioned way.
Sent from my SAMSUNG-SGH-T989 using xda premium
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
I agree. even after switching to twrp I still find the script useful. But op warning about using script with cwm version 6xxx might be true. I have issue with boot when i was on cwm 6 and i had to Odin cwm 5.0.2.7 again to get into recovery menu.
Sent from my SGH-T989 using xda app-developers app
Thanks, always forgot the formatting steps
ultratt said:
Thanks, always forgot the formatting steps
Click to expand...
Click to collapse
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
RushAOZ said:
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Davy Jones said:
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Click to expand...
Click to collapse
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
RushAOZ said:
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Oh cool, I was already really liking TWRP and this makes it even better.
This thread should be a sticky.
Khameleon said:
This thread should be a sticky.
Click to expand...
Click to collapse
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
apicia said:
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
Click to expand...
Click to collapse
Just go into CWM and wipe cache in the main menu and dalvik in the advanced menu. To be honest though you don't need to do this whatsoever. Only when dirty flashing a new nightly. In my experience atleast lol as far as gapps go..
http://goo.im/gapps/gapps-jb-20121011-signed.zip
These should work just fine
Sent from my SAMSUNG-SGH-T989 using xda premium
Bump fer new users yo
Sent from my SGH-T989 using xda premium
Bump for new users
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks
Hi,
after wiping cache and Dalvik cache, *every time I reboot my phone* I keep getting the "Upgrade android: launching applications" error message...
How can I fix this?
Tx a lot.
If you do a normal reboot (ie/ without wiping dalvik and cache) do you still get this?.....I'm guessing probably not.
When you wipe dalvik and cache, you are clearing ALL the data for your installed apps.....the "upgrading android" message you are seeing is an indication that the apps are being re-updated and is a perfectly normal occurrence under these circumstances......not an error......
Please hit thanks if this helped
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
keithross39 said:
If you do a normal reboot (ie/ without wiping dalvik and cache) do you still get this?.....I'm guessing probably not.
When you wipe dalvik and cache, you are clearing ALL the data for your installed apps.....the "upgrading android" message you are seeing is an indication that the apps are being re-updated and is a perfectly normal occurrence under these circumstances......not an error......
Please hit thanks if this helped
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, as I wrote above, this happens EVERY TIME I reboot my phone, meaning normal reboot (not going into recovery mode and deleting anything, I just did that once!)....
Then some of your apps are not compatible with your rom or you just flashed a wrong .zip or something. I believe just wiping data and reflashing will fix this.
Sent From My PACMAN Wonder Using xda-Developers app
7amada100 said:
Then some of your apps are not compatible with your rom or you just flashed a wrong .zip or something. I believe just wiping data and reflashing will fix this.
Sent From My PACMAN Wonder Using xda-Developers app
Click to expand...
Click to collapse
I did not install anything - neither new apps, nor .zip - after wiping cache+dalvik.
I tried wiping cache+dalvik another time, then rebooting normally, but I still get this message every (normal) reboot...
I meant wiping data (losing all your apps and installing them again later.
Sent From My PACMAN Wonder Using xda-Developers app
7amada100 said:
I meant wiping data (losing all your apps and installing them again later.
Sent From My PACMAN Wonder Using xda-Developers app
Click to expand...
Click to collapse
I think I'd have to agree.....it sounds like you have a problem with one of the apps and/or the ROM you have on your phone......depending on how deep the issue goes, you have two options.....
Option 1.......download "appbak" from the play store, use it to make a list of your installed apps then delete them. When you've done that, wipe cache and dalvik again (lol) and use appbak to do a fresh reinstall of all your apps........
If that doesn't work.......
Option 2.......
Wipe EVERYTHING, including your ROM, SD card, internal storage, cache and dalvik, and do a COMPLETELY "pristine" install.....if that doesn't sort it out, nothing will, and a trip to the service center is probably the only option.......
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
7amada100 said:
I meant wiping data (losing all your apps and installing them again later.
Sent From My PACMAN Wonder Using xda-Developers app
Click to expand...
Click to collapse
Well, thanks, but... I prefer keep it in this way rather than flashing again.
I'll wait for next CM9 version at least.
Is there any other method how to solve this?
Tx.
[.::MDT::.] said:
Well, thanks, but... I prefer keep it in this way rather than flashing again.
I'll wait for next CM9 version at least.
Is there any other method how to solve this?
Tx.
Click to expand...
Click to collapse
CM10 may well now be the priority......
http://forum.xda-developers.com/showthread.php?t=1990795
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
keithross39 said:
CM10 may well now be the priority......
http://forum.xda-developers.com/showthread.php?t=1990795
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
Click to expand...
Click to collapse
Or pacman. It is works pretty great even in alpha!
Sent From My PACMAN Wonder Using xda-Developers app
keithross39 said:
CM10 may well now be the priority......
http://forum.xda-developers.com/showthread.php?t=1990795
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
Click to expand...
Click to collapse
Wow, cool, I didn't notice it...
that's a good point!
Btw... is there any con with my problem?
I mean, it's annoying, but actually what's the problem (apart waiting 1min more and wasting 0,05% battery maybe) if every reboot it tries the upgrade?
[.::MDT::.] said:
Wow, cool, I didn't notice it...
that's a good point!
Click to expand...
Click to collapse
Lol....likewise....the only reason I knew, was that someone made reference to CM 10 in another post.....
And from what I've read, even though it's at initial release.....it's pretty much where CM 9 was when it was at Alpha 7......so defo looking promising.......
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
keithross39 said:
Lol....likewise....the only reason I knew, was that someone made reference to CM 10 in another post.....
And from what I've read, even though it's at initial release.....it's pretty much where CM 9 was when it was at Alpha 7......so defo looking promising.......
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
Click to expand...
Click to collapse
Yep, seems pretty interesting, the only thing that leaves me puzzled is that he's using kernel 2.6.35, not 3.x... does this mean he will have to do an entire different CM10 version later on, or will we be able to upgrade from CM10kernel2.6 to CM10kernel3.x?
Moreover, re my problem... If I want to install CM10 and get rid of this problem, I guess I'd do a full wipe... is this procedure correct?
cwm-> wipe data/factory reset
Cwm-> wipe cache
cwm->mount and storage -> format system. Format data. Format cache.
Install cm10alpha1.
Install gapps.
Thanks.
According to Arco, the reason he's sticking with v2.6 is because the camera works with it....on 3.0, it doesn't......yet....
He has said that he might try to integrate 3.0 into the build at a later date....when it's more stable.
In terms of wiping prior to installing '10....
All I've ever done before flashing a new ROM is wipe cache, dalvik and factory wipe/reset. If you want advice about anything more thorough, the best person to comment would be Pepoluan......he can guide you step by step to achieve the "pristine" result you want.....but yes, at the very least, you need to deal with cache, dalvik and factory reset......
In terms of flashing CM 10, follow my guide...
http://forum.xda-developers.com/showthread.php?t=1941028
and everything should install without issue.....
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
[.::MDT::.] said:
Hi,
after wiping cache and Dalvik cache, *every time I reboot my phone* I keep getting the "Upgrade android: launching applications" error message...
How can I fix this?
Tx a lot.
Click to expand...
Click to collapse
I got this error in two occasion after clean instal new ROM.
What I do is go to CWM, wipe everything, re-flash ROM + Gapps, wipe everything (again), restore app with titanium backup. And everything is smooth...
keithross39 said:
According to Arco, the reason he's sticking with v2.6 is because the camera works with it....on 3.0, it doesn't......yet....
He has said that he might try to integrate 3.0 into the build at a later date....when it's more stable.
In terms of wiping prior to installing '10....
All I've ever done before flashing a new ROM is wipe cache, dalvik and factory wipe/reset. If you want advice about anything more thorough, the best person to comment would be Pepoluan......he can guide you step by step to achieve the "pristine" result you want.....but yes, at the very least, you need to deal with cache, dalvik and factory reset......
In terms of flashing CM 10, follow my guide...
http://forum.xda-developers.com/showthread.php?t=1941028
and everything should install without issue.....
Click to expand...
Click to collapse
I heard someone mentioning my name
To get a "Pristine" CM9, the steps are very simple, actually. BUT, you *need* a computer (laptop or desktop, doesn't matter).
1. Create a nandroid backup, just in case
2. Copy all important non-synced files from the internal storage & internal SD into the external SD
3. Backup your external SD into the computer
4. Format your SD. If you plan on using Link2SD, this would be a good time to also repartition it.
5. Copy the CM9 and GApps updatezips to the SD card.
6. Boot into CWM5/6 recovery, and wipe: cache, data, system, internal SD, battery stats.
7. Install the two updatezips (CM9 followed by GApps).
8. Reboot. Follow the initialization procedure.
9. If you want SD-Swapping, as soon as you arrived in the Trebuchet launcher, open Settings and configure SD-swapping.
10. DO NOT EVER restore any backups you made in GB, except messages and call logs. ALWAYS install apps fresh from the Play Store.
With a Pristine install, I *never* had any problems. And my phone's responsive enough I honestly no longer feel even the slightest desire to install any tweaks/mods/'engines'.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Tx u all, I've just upgraded to CM10a1 and the problem is gone!
What I did:
reboot into CWM
NANDROID BACKUP
wipe cache
wipe dalvik cache
wipe data/factory reset
wipe battery stats
wipe internal memory (/sdcard)
installed CM10a1 zip from /external_sdcard
installed gapps for CM10a1 from /external_sdcard
fix permissions
reboot
[.::MDT::.] said:
Tx u all, I've just upgraded to CM10a1 and the problem is gone!
What I did:
reboot into CWM
NANDROID BACKUP
wipe cache
wipe dalvik cache
wipe data/factory reset
wipe battery stats
wipe internal memory (/sdcard)
installed CM10a1 zip from /external_sdcard
installed gapps for CM10a1 from /external_sdcard
fix permissions
reboot
Click to expand...
Click to collapse
Good job mate...
Just one point....I noticed you mentioned creating a nandroid backup......there is a good chance that if you use that backup, the issue you had will return......
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
keithross39 said:
Good job mate...
Just one point....I noticed you mentioned creating a nandroid backup......there is a good chance that if you use that backup, the issue you had will return......
From my Galaxy W on CM9 and CWM6 with Tapatalk 2
Click to expand...
Click to collapse
Yeah, I hope I'll not need it anyway!