Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
RampageRR said:
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
Click to expand...
Click to collapse
you got it. i dont think you have to flash the script everytime and you will not have to flash gapps everytime. btw you dont have to wipe between nightlys just simply flash over
Thanks, I appreciate the quick reply. So I shouldn't bother to wipe cache and dalvik cache? I thought that was pretty much recommended before flashing the majority of stuff. Ok, so I'm off to flash this nightly.
I never wipe between nightlys. But if you ever do encounter problems, then wipe cache, dalvik cache then reflash
Sent from my Desire HD using XDA Premium App
I've always wiped cache and dalvic between nightlies. I don't know if it's needed but I've never had any problems with installs. It only takes a few seconds and it's never hurts to be safe.
Sent through the power of Cthulhu!
I flashed 144, no issues so far. Thanks to all of you for the replies. I ended up wiping cache and dalvik cache just to be safe. I know there's a change log, but has there been any changes of consequence over 7.1 RC that are noticeable?
I know the most easily noticeable is if you put a lock screen on you can disable the lockscreen. Plus from 143 on is now on 2.3.5 if I'm not mistaken which does have some slight tweaks.
Sent through the power of Cthulhu!
Related
Sorry, this might be kind of a noob question, but i see build 23 is out for CM7. If i flash the new build, do i need to totally set up my phone all over again?
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Genocaust said:
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Click to expand...
Click to collapse
Thanks. Ugh, i didn't even think about that when i flashed CM7. Seems like it is a real PITA to wipe every time and have to configure all the settings again.
I had good success on my move from stock -> Ice Glacier (un-crapwared stock) by making a full TitaniumBackup of -everything- and then restoring it app by app (along with settings). They are similarly built ROMs, and it worked well for me with minimal downtime. You may want to consider trying that if you are just changing between CM flavors, as I would presume they are mostly backward compatible with a few fixes/features here and there. At worst it may leave you with just system settings to redo.
When i flash a new CMNightly all i do is wipe the cache and the Dalv/Cache and i've yet to have any problems. If you are worried about wiping and restoring everything. you might want to look into Titanium Backup.
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
shortskoolbus said:
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wiping the Cache and wiping the Dalv Cache will not reset the phone. Only a full wipe will do that.
To my understanding, a "full wipe/factory reset" in Clockwork Recovery will only clear /cache, /data, and Davlik cache. /boot and /system will not be touched. Some users moving from Froyo to Gingerbread have had problems with /system, and a wipe of /system (from within Clockwork Recovery or from adb) has solved some problems for people, beyond what a full wipe can do. Discussions are in the CM7 thread in the Application Development subforum.
I know, most people refuse to search for anything.
i usually wipe the Cache and the Dalv Cache when updating nightlies, but several times i've wiped nothing and just flashed the new one on top and its always worked just fine for me
I always do a full wipe when installing roms. Setting it up each time makes me think its a whole new phone which is cool.
You do NOT need to wipe when upgrading to a new version of the same ROM. I've probably flashed 10 no-wipe updates of cm7 on my phone and it's still perfectly stable, no force closes or anything.
Boot into recovery and wipe cache and dalvik cache before flashing. Give it a few mins to "settle" on the first boot, reboot again and you're good to go.
Worst-case scenario you'll just wipe and reflash anyway, and nothing lost.
I have tried several ROMS and it's sad i have no success with CM& and Fauxs AOSP.. What could be the problem? Thankx
ok it seems alot of people are having problems flashing this particular rom. listen i do it like this and i neve, EVER have a problem so try this
now put the rom (zip) on ur sdcard im sure u know how, then from there wipe data, wipe cache, then go into advanced and wipe dalvik, THEN u install the rom, alot of people are doing it reverse do it like this ok so after the rom is installed, install the gapps rite after the rom. then boot ur phone up let it sit 5 minutes..........now if u want a custom kernel go back into recovery and wipe just cache and dalvik, no need to wipe data. ok so after u wipe cache then dalvik install the kernel and u are done boot up and enjoy!
sarni84 said:
ok it seems alot of people are having problems flashing this particular rom. listen i do it like this and i neve, EVER have a problem so try this
now put the rom (zip) on ur sdcard im sure u know how, then from there wipe data, wipe cache, then go into advanced and wipe dalvik, THEN u install the rom, alot of people are doing it reverse do it like this ok so after the rom is installed, install the gapps rite after the rom. then boot ur phone up let it sit 5 minutes..........now if u want a custom kernel go back into recovery and wipe just cache and dalvik, no need to wipe data. ok so after u wipe cache then dalvik install the kernel and u are done boot up and enjoy!
Click to expand...
Click to collapse
I've done this several times.. Mine doesn't even go pass the LG bootscreen and have to pull battery to restart phone. What i also notice is when installs the ROM, it doesnt extract the file, it just goes locating and updating. weird. never had this problem with Bionix 2, EB and ultimate. Thank you!
I'm coming from an og Verizon Droid and we used to go into he partion menu and I'd wipe the system as well..i always wipe everything a few times b4 i flash any new rom
Sent from my LG-P999 using XDA Premium App
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
My Wifi-Only US Xoom is rooted with the universal xoom root, and has the EOS-Wingray-60 Rom successfully installed, but everytime I try to download Gapps, this comes up:
How do I fix that?
EDIT: That is no longer the problem. Everytime I flash Gapps now, my xoom ALWAYS gets stuck on the dual core screen after reboot.
Double EDIT: I was too lazy to stock flash it, so I simply wiped everything again, downloaded EOS wingray 60, Then I wiped my cache and my dalvik (Not data), then reinstalled Gapps, and fixed permissions and it finally loads now. Thank ****ing god.
Can anyone help me with this please??
Slayergramp said:
Can anyone help me with this please??
Click to expand...
Click to collapse
Okay
1. Dont use v9 gapps you should always use latest v10.5 is the latest...
2. Check the md5 of the file
3. Wipe cache and dalvik cache
4. Install said gapps
5. Fix permissions
6. Win
Sent from my mind control device
Where's v10.5?
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Slayergramp said:
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Click to expand...
Click to collapse
Go to the eos rom.. There is a gapps link.. Click it and it will take you to all the gapps packages ... Download 10.5 check the md5
Sent from my mind control device
Goo-inside.me/roms/teameos/gapps
Download the most recent EOS gapps from there. The (bad) in your attempted install means the zip is corrupt.
Sent from my MB860 using xda premium
Alright, so my problem continues. I was running stock unrooted ICS, then flashes recovery. Then I wiped data, cache and dalvik. Then I rooted with the Xoom universal root. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, and flashes eos Rom 60. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, successfully installed gapps 10.5 for the first time, it wasn't (bad). Rebooted, andddd stuck. After I rebooted in permanately stuck on the dual core Motorola logo thing. What did I do wrong?
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
okantomi said:
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
Click to expand...
Click to collapse
When I flash them, is there anything I need to wipe or clear? Or do I leave everything alone?
God Dammit! This is pissing me off!!!!!!!!!!!!!!!!!!!!! It ****ing takes for ever to upgrade back to ICS when I have to flash the ****ing stock of 3.0!!!
I upgraded to ICS, after flashing 3.0, I flashed the R4c Recovery, I did a factory reset, and wiped Dalvik and Cache, then I installed the Universal root (Is there a different root I should use?), then I went back (Still in recovery mode) and did a factory reset, and wipe cache and dalvik. Then I install Wingray-60, then *immediately after* I installed Gapps v10.5!!!! I rebooted and my ****ING xoom is stuck on the dual core screen AGAIN!!!
WHAT THE ****.
Not quite sure what those first few steps were, but boot to recovery, go to mounts and storage and wipe system and cache, then go to the wipe menu and do a data wipe and dalvik wipe.
Then flash ICS and gapps.
Shouldn't have any problems after that unless your Xoom doesn't like ICS for some strange get reason.
Sent from my Xoom using xda premium
Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.
What version of CWM are you running?
You should be fine, but it never hurts to check. You flash a JB rom just like any other. Wipe wipe wipe and flash.
The whole wipe wipe wipe is completely unnecessary. One wipe is sufficient and any additional won't do anything.
It's like saying that unless you wipe exactly 3 times the Android Gods are going to demand a human sacrifice for your phone to boot.
lol i think dvorak meant wipe cache, wipe dalvik cache, wipe data (wipe wipe wipe) but that's my take..
anyway, if you can flash MIUI ICS with whatever CWM version you currently have, you should be able to flash other JB ROM. Nandroid as always.. Goodluck!
Sent from my Nexus S using xda premium
jacob66 said:
Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.
Click to expand...
Click to collapse
This is what I did :
1. Boot into recovery and perform a nandroid backup of my MIUI installation.
2. Wipe.
3. Flash XenonHD 9 JB ROM + marmite 4.2 kernel.
My phone is running really smooth now. Good luck.
[email protected] said:
lol i think dvorak meant wipe cache, wipe dalvik cache, wipe data (wipe wipe wipe) but that's my take../QUOTE]
Yep, that's it. Of course wiping everything 3 times would be unnecessary.
Click to expand...
Click to collapse
jacob66 said:
Hey, I'm currently on MIUI ics. I know I have to wipe/factory reset everything. But is it safe to flash on the current CWM? Or do I need to update it or something? Do I just flash the new JB rom like I would switching from MIUI to a stock ics rom? I'm a noob, sorry if this doesn't make sense.
Click to expand...
Click to collapse
if you get a cluster f*#@ of problems then clean install. It isn't that hard. Use Titanium Backup and good to go.
In Recovery:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with only bootloader, recovery and radio...dalvik-cache resides on /data, so it's gone already.
3. flash rom
4. gapps & custom-kernel (if needed). No need to let the phone boot & settle before flashing them (most custom-kernels have a script that automatically wipes /cache & dalvik during kernel-install)
5. reboot
6. Run TB -- restore missing apps with data --1st option under restore
just updating rom:
1. flash rom-zip
2. wipe /cache and dalvik-cache
3. reboot
Do this before reporting any issues on the thread since the problems are often related to this and not the ROM or kernel.