Related
I have cyanogen mod 7.1.0 RC 1-vision installed on G2 already. Can somebody explain to me how I get to v 2.3.5? I know it has something to do with nightly builds and xboarder56. Im just a little confused on how and what order to flash things. Do I have to install every Nightly update or will the newest one be fine? And exactly what it xboarder56? Is that a modification of Cyanogensmod?
Thanks Sean.....
just install the newest nightly and youll have 2.3.5
xboarder56 is a guy that made a thread on how to install the stock launcher over the ADWlauncher
but you can alternately download a gingerbread launcher from the market and install it
Wipe, and flash the newest nightly just how you flashed RC1
Sent from my T-mobile G2 using Tapatalk
download the latest nightly, put on your SDcard
1) enter recovery (power button -> reboot -> 'recovery')
2) 'backup and restore' -> backup current ROM
3) wipe cache, advanced -> wipe dalvik cache
4) 'Install zip from SDcard' -> Flash nightly.zip
5) reboot
6) fix permissions (ROM manager -> 'fix permissions'
7) reboot again
xboarder56 is a dev on here. he makes several different mods for CM7. The main one that people use is to put the stock GB launcher on CM7. CM7 by default has ADW launcher, but some prefer the stock one. Xboarder56 isn't the only one that has a stock launcher.zip available.
If you want the stock launcher, check the post in my sig. follow the directions carefully if you intend to re-flash nightlies and want to keep your screen placement.
Do I have to download each nightly build? Or can I skip builds from time to time? Are these beta builds? and if so any idea on a final version?
Thanks... Sean...
slufoot69 said:
Do I have to download each nightly build? Or can I skip builds from time to time? Are these beta builds? and if so any idea on a final version?
Thanks... Sean...
Click to expand...
Click to collapse
You can download and install every nightly. But you dont HAVE to. There is a group that only flashes one every few weeks. Either way you will be fine but if you want to be on the cutting edge of new features i would recommend installing it every day. For our phone specifically they come out between 115 am and 130 am. Like said above, wipe cache wipe dalvik install nightly fix permissions reboot with each nightly
Sent from my HTC Vision using xda premium
Question about the wipe cache and wipe dalvik? I see the option to wipe cache but I dont see the option to wipe dalvik... Sorry but I am just now starting to do differnet things with my phone and alot of this stuff is new to me...
Thanks... Sean...
slufoot69 said:
Question about the wipe cache and wipe dalvik? I see the option to wipe cache but I dont see the option to wipe dalvik... Sorry but I am just now starting to do differnet things with my phone and alot of this stuff is new to me...
Thanks... Sean...
Click to expand...
Click to collapse
Dalvik cache is under advanced. I believe if you're not running Apps2SD you can go without it.
Sent from my HTC Vision using XDA App
funkeee said:
Dalvik cache is under advanced. I believe if you're not running Apps2SD you can go without it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Apps2SD has nothing to do with the Dalvik cache. Wipe it regardless of whether or not you use Apps2SD (which is unneeded unless ur still on a G1).
Sent from my HTC Vision using XDA App
slufoot69 said:
Do I have to download each nightly build? Or can I skip builds from time to time? Are these beta builds? and if so any idea on a final version?
Click to expand...
Click to collapse
They are effectively beta builds. They're not official and not necessarily meant for the general flashing community, as they often contain bugs and untested changes.
slufoot69 said:
Question about the wipe cache and wipe dalvik? I see the option to wipe cache but I dont see the option to wipe dalvik... Sorry but I am just now starting to do differnet things with my phone and alot of this stuff is new to me...
Click to expand...
Click to collapse
like I said above, its under advanced -> wipe dalvik cache.
It has nothing to do with Apps2SD. On a related note, there's no need to run Apps2SD unless you have several gigantic games or something filling up internal memory. You should have more than enough internal memory to keep all apps on the phone itself.
When I wipe my Dalvik Cache, CWM says it cannot find the drive/partition for it. Its never caused a problem for me. I assumed it was due to sdcard partitions, which I used to use for Swap and Apps2SD only. Is it an internal memory partition for performance related caching? If so somethings messed up with my partitions.
Sent from my HTC Vision using XDA App
funkeee said:
When I wipe my Dalvik Cache, CWM says it cannot find the drive/partition for it. Its never caused a problem for me. I assumed it was due to sdcard partitions, which I used to use for Swap and Apps2SD only. Is it an internal memory partition for performance related caching? If so somethings messed up with my partitions.
Click to expand...
Click to collapse
What exactly is it saying? usually it will throw an error about SD-EXT. disregard the error.
For me when I flash new ROMs I use Superwipe+ to do all my wiping in one step. Its quick and effective.
Check it out:
http://forum.xda-developers.com/showthread.php?t=1044992
Each and every morning, I make it my habit to launch Rom Manager (paid version), and select 'Check for updateds'. After it tells me there's an update available, I approve it and select to download (via wifi) gapps. Once it done downloading it then prompts me to choose wipe data & cashed, backup existing rom, or wipe dalvik cashe. I always select wipe Dalvik cashe, then I approve it to power off.
Bamb! easy sneesy .. My nightly rom gets updated!
Sent from my HTC Vision using xda premium
martonikaj said:
download the latest nightly, put on your SDcard
1) enter recovery (power button -> reboot -> 'recovery')
2) 'backup and restore' -> backup current ROM
3) wipe cache, advanced -> wipe dalvik cache
4) 'Install zip from SDcard' -> Flash nightly.zip
5) reboot
6) fix permissions (ROM manager -> 'fix permissions'
7) reboot again
Click to expand...
Click to collapse
I had the same question as the OP. I've been running CM v.7.1 RC1 for a while now and I love it. But I would like to check out the nightlies. Just so I am clear, to go from my current ROM to the latest nightly, I only need to to wipe cache and dalvik cache - and that's it? Somehow I thought the process was more difficult. I thought I'd have to restore my apps with TB and reconfigure all my settings...
And one last quick question. I've never needed to run 'fix permissions.' The sole FC I get is with LauncherPro, but only when I reboot. It doesn't bother me, and it seems like I've read about users who have problems after running the 'fix permissions' in RM. Can anyone elaborate on why that might be?
Thanks so much, guys.
Ditamae said:
I had the same question as the OP. I've been running CM v.7.1 RC1 for a while now and I love it. But I would like to check out the nightlies. Just so I am clear, to go from my current ROM to the latest nightly, I only need to to wipe cache and dalvik cache - and that's it? Somehow I thought the process was more difficult. I thought I'd have to restore my apps with TB and reconfigure all my settings..
Click to expand...
Click to collapse
upgrading from an older version of CM7 to a Nightly you don't have to wipe data. Just cache/dalvik and flash the nightly.
And one last quick question. I've never needed to run 'fix permissions.' The sole FC I get is with LauncherPro, but only when I reboot. It doesn't bother me, and it seems like I've read about users who have problems after running the 'fix permissions' in RM. Can anyone elaborate on why that might be?
Click to expand...
Click to collapse
Fixing permissions is just a good rule of thumb to follow after flashing a new ROM so all your apps are setup properly. I haven't heard of Fix Permissions breaking anything.
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
thanks!
hoopsdavis said:
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
Click to expand...
Click to collapse
Battery stats eh? cool didnt know that one! Thanks man! Going to rock this now.
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
nice.
okantomi said:
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
Click to expand...
Click to collapse
Thanks everyone for the help rocking EOS!
lol i just wish you didnt have to wipe everything....
lucky
alex94kumar said:
lol i just wish you didnt have to wipe everything....
Click to expand...
Click to collapse
I was lucky and hadn't put too much on it. So the wipe wasn't a big deal, if I'm right don't have to wipe every time to update build so was worth it. As a lot say my Xoom a lot snappier now. Would recommend doing it!
Wiping is usually the best way to go. There are workarounds, but the effort it takes to do so kinda outweighs the result.
so my question is....
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
TheLostXoom said:
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
Click to expand...
Click to collapse
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
bacon612 said:
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
TheLostXoom said:
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
Click to expand...
Click to collapse
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
okantomi said:
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
Click to expand...
Click to collapse
When first flashing a nightly a nandroid backup is recommended but it's not that necessary when going from your first nightly to another nightly. At least I don't do that because I'd rather hasten the whole data wipe/flash process and it works for me.
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
gfreh said:
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
Click to expand...
Click to collapse
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
krushnam said:
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
Click to expand...
Click to collapse
Hi! Thanks for the reply, and sorry for my English.
Actually, I have already installed CM7 and it worked fine, except for the Market app. Trying to solve this, I have done a factory reset from stock recovery and, since that, CM7 is locked to the boot screen.
And yes, I have installed CM7 through CWM recovery, and I'm using a MB525 Defy.
Well, I have just tried wiping Dalvik Cache, but it seem as if nothing happens when I select this.
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
krushnam said:
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
Click to expand...
Click to collapse
How can I wipe market data? It is not an option from CWM...
gfreh said:
How can I wipe market data? It is not an option from CWM...
Click to expand...
Click to collapse
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
thiagoelg said:
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
Click to expand...
Click to collapse
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
gfreh said:
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
Click to expand...
Click to collapse
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
krushnam said:
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
Click to expand...
Click to collapse
Hi,
I have just reflashed a retailer version using RSD on a friend's computer and it is now back to life... now I'm figuring out what is the best path to follow.
Thanks for the help!
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
sa3e1 said:
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
Click to expand...
Click to collapse
Yeah... I know that. I just wanted to rollback everything and have the phone back. I'm now studying which is the best ROM for me to install again, but meanwhile, I have my phone working.
This is my first android phone and therefore cm10.1 is the first ROM I've ever had so I've never updated my ROM before. Goo manager sent me a notification saying that Cm10.1 rc2 is now available but in order to download it do I have to wipe my phone to factory default or can I just install it over my old cm10.1 and keep my apps and stuff?? Thanks
michaelsp9 said:
This is my first android phone and therefore cm10.1 is the first ROM I've ever had so I've never updated my ROM before. Goo manager sent me a notification saying that Cm10.1 rc2 is now available but in order to download it do I have to wipe my phone to factory default or can I just install it over my old cm10.1 and keep my apps and stuff?? Thanks
Click to expand...
Click to collapse
The whole point of the CM updater is that you don't have to wipe anything - not data, not cache. Just start the download, click OK to install when it finishes downloading, and it'll flash itself over your previous installation. The same applies to downgrading to an earlier release - no wipe needed.
Yes, you can keep your apps and system settings. No need to backup and restore - they'll be exactly the way they were before you downloaded the update.
However, if you are migrating to an entirely different ROM (i.e. not the official CM), then yes, you probably need to wipe. Going back and forth between different updates of the same ROM doesn't need wiping though.
You can just flash it normally using CWM. It's called Dirty Flashing. DO clear Cache and Dalvik before flashing
sigma392 said:
You can just flash it normally using CWM. It's called Dirty Flashing. DO clear Cache and Dalvik before flashing
Click to expand...
Click to collapse
So what do I do just download the ROM and its gapps again and flash them both? Which one first?
michaelsp9 said:
So what do I do just download the ROM and its gapps again and flash them both? Which one first?
Click to expand...
Click to collapse
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
sigma392 said:
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
Click to expand...
Click to collapse
No need to flash Gapps again on CM, unless data is wiped because of the b/u scripts.
The updater script in the ROM also wipes the Dalvik for you.
sigma392 said:
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
Click to expand...
Click to collapse
Actually you don't have to do any of that except flash the rom and reboot. All the rest is automatic.
I reverted to my backup that I made before flashing. Franco kernel didn't work and I had all the crappy apps I uninstalled from cm10.1 like Apollo and stuff .. What's new is rc2 anyways?
updating cm10.1
Hi all
I am currently using cmw6.0.2.3 and rom cm10.1.20130411-EXPERIMENTAL-p3100-M3 and would like to switch to using cm10.1 nightly. Reason to switch is because pie control in M3 is not working and I saw in some video that it is working in nightly. May i know how to update usingmanual mode please? And also will it deketenall my installed apps and data?
Thanking you all in advance
People,
1) Nandroid Backup.
2) Dirty Flash, if something doesn't work or it starts to fails, restore nandroid, backup everything (needed) with Titanium backup or similar, wipe everything, flash, restore, win.
I have a Nexus 4.
To flash a kernel all I need to do is to go to recovery mode,
Install zip from sd card,
Choose zip from SD card,
Pick the kernel's zip file,
Press yes and reboot the system?
Don't I need to wipe anything like when flashing a new rom?
And should I flash the kernel and then the ROM and GApps,
Or flash the ROM and GApps and then flash the kernel?
If my device acts weird after I flashed the kernel,
And I did a nandroid backup before that (I backed up with a ROM and stock kernel),
After I restore it, will everything be like what it was before I flashed the kernel (Will I have to flash the ROM again?)
Thank you in advance guys!
Yes thats how you install a kernel. Some people say to wipe cache and dalvik after installing, but its up to you.
Flash rom, gapps, then kernel.
When you restore the nandroid it will restore everything, including the rom and kernel that were installed at the time of taking the backup.
So yes...if stuff starts acting up, and you restore your nandroid that you took while on stock rom/kernel it should fix the issues. You dont have to flash the rom again...its included in the nandroid.
chromium96 said:
Yes thats how you install a kernel. Some people say to wipe cache and dalvik after installing, but its up to you.
Flash rom, gapps, then kernel.
When you restore the nandroid it will restore everything, including the rom and kernel that were installed at the time of taking the backup.
So yes...if stuff starts acting up, and you restore your nandroid that you took while on stock rom/kernel it should fix the issues. You dont have to flash the rom again...its included in the nandroid.
Click to expand...
Click to collapse
What will be different if I'll wipe cache and dalvik or not?
VIPOA said:
What will be different if I'll wipe cache and dalvik or not?
Click to expand...
Click to collapse
Not 100% sure, but f you wipe them your dalvik will be rebuilt on the next boot, and your cache will also be rebuilt once the system actually boots.
Theres no harm in wiping them.
VIPOA said:
What will be different if I'll wipe cache and dalvik or not?
Click to expand...
Click to collapse
you never have to wipe anything when flashing a kernel, nothing, regardless of what others say. the dalvik nor the cache have anything to do with kernels. its like taking a shower and washing your socks to put gas into your car.
chromium96 said:
Not 100% sure, but f you wipe them your dalvik will be rebuilt on the next boot, and your cache will also be rebuilt once the system actually boots.
Theres no harm in wiping them.
Click to expand...
Click to collapse
So my device will be OK if I'll wipe dalvik and cache before I flash a kernel, right?
simms22 said:
you never have to wipe anything when flashing a kernel, nothing, regardless of what others say. the dalvik nor the cache have anything to do with kernels. its like taking a shower and washing your socks to put gas into your car.
Click to expand...
Click to collapse
When you flash a kernel, do you wipe anything?
VIPOA said:
So my device will be OK if I'll wipe dalvik and cache before I flash a kernel, right?
When you flash a kernel, do you wipe anything?
Click to expand...
Click to collapse
your device will be ok wiping dalvik and cache, but there is no need to do it. there is never any need to wipe anything when flashing a kernel.
simms22 said:
your device will be ok wiping dalvik and cache, but there is no need to do it. there is never any need to wipe anything when flashing a kernel.
Click to expand...
Click to collapse
Do you wipe anything when you flash a kernel?
And does your kernel works OK without wiping?
VIPOA said:
Do you wipe anything when you flash a kernel?
And does your kernel works OK without wiping?
Click to expand...
Click to collapse
no, i dont. and it works great.
simms22 said:
no, i dont. and it works great.
Click to expand...
Click to collapse
OK. Thank you very much for the help
One last question, which kernel should I flash with PA?
FRANCO or TRINITY?
VIPOA said:
OK. Thank you very much for the help
One last question, which kernel should I flash with PA?
FRANCO or TRINITY?
Click to expand...
Click to collapse
try both, they are both good kernels. i use trinity, but francisco makes a good kernel too.
simms22 said:
try both, they are both good kernels. i use trinity, but francisco makes a good kernel too.
Click to expand...
Click to collapse
And two last questions,
How do I update a ROM?
Should I delete the zip files of previous Roms and kernels and keep only what I'm using (let's say PA 3.60 and Trinity/Franco kernels)?
VIPOA said:
And two last questions,
How do I update a ROM?
Should I delete the zip files of previous Roms and kernels and keep only what I'm using (let's say PA 3.60 and Trinity/Franco kernels)?
Click to expand...
Click to collapse
if you want, keep the current rom/kernel and the previous. thats probably the smartest way, in case one is buggy. but, at least, keep a copy of the current rom/kernel in your storage at all times, itll save you headaches later.
when you update a rom, flash it in your custom recovery. flash the rom, gapps if needed, and the kernel, the reboot. if youre just updating, you dont have to wipe anything. but if you are flashing a new rom, you do have to wipe data/factory reset.
simms22 said:
if you want, keep the current rom/kernel and the previous. thats probably the smartest way, in case one is buggy. but, at least, keep a copy of the current rom/kernel in your storage at all times, itll save you headaches later.
when you update a rom, flash it in your custom recovery. flash the rom, gapps if needed, and the kernel, the reboot. if youre just updating, you dont have to wipe anything. but if you are flashing a new rom, you do have to wipe data/factory reset.
Click to expand...
Click to collapse
OK
Thank you very much for the help
Will my ROM's settings be saved?
VIPOA said:
OK
Thank you very much for the help
Will my ROM's settings be saved?
Click to expand...
Click to collapse
if you are just updating, yes.
simms22 said:
if you are just updating, yes.
Click to expand...
Click to collapse
Can I use this and will it be OK (no bugs)?
http://forum.xda-developers.com/showthread.php?t=2227226
VIPOA said:
Can I use this and will it be OK (no bugs)?
http://forum.xda-developers.com/showthread.php?t=2227226
Click to expand...
Click to collapse
Always use your recovery to flash stuff its the safest way.
Sent from my Nexus 4
spaceman860 said:
Always use your recovery to flash stuff its the safest way.
Sent from my Nexus 4
Click to expand...
Click to collapse
OK
Thank you very much guys!