Question. If I want to install Stable CM 7.2 on my rooted Defy thru Custom Recovery can I use my stock froyo kernal 2.2 that came with Tmobile US phone or do I need to flash a different froyo kernal? Thx for your patience. Noob
wildcatbyrne said:
Question. If I want to install Stable CM 7.2 on my rooted Defy thru Custom Recovery can I use my stock froyo kernal 2.2 that came with Tmobile US phone or do I need to flash a different froyo kernal? Thx for your patience. Noob
Click to expand...
Click to collapse
Use the CM7.2 build for froyo kernel. You don't need to flash any other kernel.
Cm7.2 to MiuiAndroid
Hai I m on Cm 7.2 . I want to flash miuiandorid Gb rom . Ca i i flash straight away or need to go back to the froyo and then flash ?
ChallengerLPF said:
Hai I m on Cm 7.2 . I want to flash miuiandorid Gb rom . Ca i i flash straight away or need to go back to the froyo and then flash ?
Click to expand...
Click to collapse
Just do a full wipe and flash through recovery.
maniac103 or quarx stable unofficial
If I wanted to go directly to Maniac or Quarx stable unofficial 7.1 .01 from my stock froyo TMobile, do I need to flash another spf froyo first?
Thx
wildcatbyrne said:
If I wanted to go directly to Maniac or Quarx stable unofficial 7.1 .01 from my stock froyo TMobile, do I need to flash another spf froyo first?
Thx
Click to expand...
Click to collapse
Maniac's one is the most up to date and polished I think as he's the only
one that actively since works on GB.... Quarx stable is really old but still a great rom
and since you're already rooted with clockworkmod you don't need to flash a sbf..... Just full
wipe data and cache wipe then dalvik cache..... Good luck and I hope you enjoy your experience
Don't install CM7.2 if you want battery life .
I only get 8hs of battery with light use and with ms2ginger 3.0 gets 12hs of battery life with wi-fi , browsing and somes games
Try MS2ginger 3.0 + greenbread mod (ms2ginger 4.0 lags with green lens) , this rom have a gingerbread kernel (no battery drops and better battery backup) :good::good::good: or Whiterabbit 1.6 (custom cm7)
ms2ginger : http://forum.xda-developers.com/showthread.php?t=1140839
whiterabbit : http://forum.xda-developers.com/showthread.php?t=1510063
Kayant said:
Maniac's one is the most up to date and polished I think as he's the only
one that actively since works on GB.... Quarx stable is really old but still a great rom
and since you're already rooted with clockworkmod you don't need to flash a sbf..... Just full
wipe data and cache wipe then dalvik cache..... Good luck and I hope you enjoy your experience
Click to expand...
Click to collapse
Presently running Stable 7.2 . You mean I can install Maniacs latest build by just wipe data and cache and install Maniacs zip. Do I need to reinstall Gapps and wipe Dalvik.
Thx again
wildcatbyrne said:
Presently running Stable 7.2 . You mean I can install Maniacs latest build by just wipe data and cache and install Maniacs zip. Do I need to reinstall Gapps and wipe Dalvik.
Thx again
Click to expand...
Click to collapse
You may not even need to wipe data but It's advised or at least I do it so I have not problems with my apps. If you do wipe data remember to backup first and when restoring try not to restore data of system apps that's where most issues arise from. If you don't wipe data then cache and davlik wipe install the rom then i would cache and davlik wipe again for safe measure and reboot and enjoy. Yes you will need to reflash gapps if you data wiped. You have a green lens defy right??? You only need a kernel if you have a red lense defy. Good luck.
Kayant said:
You may not even need to wipe data but It's advised or at least I do it so I have not problems with my apps. If you do wipe data remember to backup first and when restoring try not to restore data of system apps that's where most issues arise from. If you don't wipe data then cache and davlik wipe install the rom then i would cache and davlik wipe again for safe measure and reboot and enjoy. Yes you will need to reflash gapps if you data wiped. You have a green lens defy right??? You only need a kernel if you have a red lense defy. Good luck.
Click to expand...
Click to collapse
Thx for the great info!
maniac vs cm7.2 stable
Kayant said:
You may not even need to wipe data but It's advised or at least I do it so I have not problems with my apps. If you do wipe data remember to backup first and when restoring try not to restore data of system apps that's where most issues arise from. If you don't wipe data then cache and davlik wipe install the rom then i would cache and davlik wipe again for safe measure and reboot and enjoy. Yes you will need to reflash gapps if you data wiped. You have a green lens defy right??? You only need a kernel if you have a red lense defy. Good luck.
Click to expand...
Click to collapse
Running CM7.2stable without any problems. What are the advantages or improvements on unofficial stable release on Maniac103?
Thx
Related
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.
Hello,
I have old Defy with Bayer module. Which software is better for me? I heard that GB kernel has a bug - full CPU thortle. But when it happens ? Does CM9 have any other bugs ? And is it possible to record videos on this?
Thank you for answers !
Hi,
which Kernel is better is related to the software you are using. But you can't be wrong to use the CM7 Kerner with Quarx newest builds. If you want to use Cyanogenmod 9 I would also recommend you to stay on Froyo-Builds, it causes less problems with the camera.
Im of course considering proper kernel for proper CM7 version.
If you use CM7, I see no reason to change to a GB-Kernel-Version, cause it makes nothing better. In additional the newest nighties are made by Quarx for the Froyo-Kernel. See on ge. tt/8rDd1nC
Edit: No space between the dot and the t
But I've heard that GB kernel is much faster... This problem with max CPU use is problem of soft and will be never fixed on this kernel ?
kernel doubt
hi sorry to bother you
i flashed cm7.1.0-rc1.5-jordan-signed.zip a couple months ago, working fine.
i've been wanting to try out the new cm9 builds.
mi kernel version is [email protected]# 1 i dont know if this "froyo kernel" o "gingerbread kernel"
1_which rom sould i flash... quarx (29 jan) or epsylon3 ( 31 jan)?
2_do i need to flash another kernel previously?
3_what steps do i need to take to flash it?
4_will i be able to downgrade back to froyo 2.2.1 or at least my current cm7 ?
thanks a million
matias
elendil1310 said:
hi sorry to bother you
i flashed cm7.1.0-rc1.5-jordan-signed.zip a couple months ago, working fine.
i've been wanting to try out the new cm9 builds.
mi kernel version is [email protected]# 1 i dont know if this "froyo kernel" o "gingerbread kernel"
1_which rom sould i flash... quarx (29 jan) or epsylon3 ( 31 jan)?
2_do i need to flash another kernel previously?
3_what steps do i need to take to flash it?
4_will i be able to downgrade back to froyo 2.2.1 or at least my current cm7 ?
thanks a million
matias
Click to expand...
Click to collapse
1) both roms use froyo kernel, so you can try anyone.
2) you don't have to flash any kernel, cm7 uses froyo kernel aswell
3) I've just flashed 31Jan, I was using cm7 previously. What i did:
-reboot, when the motorolla logo displays, wait for the blue led to show and then press volume down.
-then you go to recovery, latest recovery. (I highly recomend to do a backup (nandroid) before wiping data)
-wipe data/factory reset, wipe cache.
-install from zip file, and choose either 29jan or 31jan zipfile. (remeber 31jan has gapps included, if you go for 29jan you should install gapps too)
-wipe cache.
-go to advanced, wipe dalvik cache.
-reboot!
First time to boot will take some minutes.
4) If you want to get back to cm7, just recover your backup (nandroid) or follow the same steps in 3) but installing cm7 zipfile.
Hope it helps you, if any more experienced user finds an error in what i've said, please correct me.
fedexmagno said:
1) both roms use froyo kernel, so you can try anyone.
2) you don't have to flash any kernel, cm7 uses froyo kernel aswell
3) I've just flashed 31Jan, I was using cm7 previously. What i did:
-reboot, when the motorolla logo displays, wait for the blue led to show and then press volume down.
-then you go to recovery, latest recovery. (I highly recomend to do a backup (nandroid) before wiping data)
-wipe data/factory reset, wipe cache.
-install from zip file, and choose either 29jan or 31jan zipfile. (remeber 31jan has gapps included, if you go for 29jan you should install gapps too)
-wipe cache.
-go to advanced, wipe dalvik cache.
-reboot!
First time to boot will take some minutes.
4) If you want to get back to cm7, just recover your backup (nandroid) or follow the same steps in 3) but installing cm7 zipfile.
Hope it helps you, if any more experienced user finds an error in what i've said, please correct me.
Click to expand...
Click to collapse
Correction in 4th point ---
for restoring ur Nandroid Backup
1. Do a factory Reset/Data wipe
2. Install CM7.zip
3. Go to restore and Restore the Nandroid that u want to restore.
4. Wipe Dalvik Cache ( Don't wipe cache partition)
5. Reboot
kanna91 said:
Correction in 4th point ---
for restoring ur Nandroid Backup
1. Do a factory Reset/Data wipe
2. Install CM7.zip
3. Go to restore and Restore the Nandroid that u want to restore.
4. Wipe Dalvik Cache ( Don't wipe cache partition)
5. Reboot
Click to expand...
Click to collapse
Thanks for the correction, but I've just came back to CM7 by restoring my old nandroid, without wipe and worked well.
camera doesn't work.and some small bugs
If you use CM7
If you use CM7, I see no reason to change to a GB-Kernel-Version, cause it makes nothing better. In additional the newest nighties are made by Quarx for the Froyo-Kernel. See on ge. tt/8rDd1nC
Hello everybody, as stated i title, i need a noob-mode step by step guide to install the new superb innatural quarx's '2ndboot-CM10' in my green lense 525 with the latest CM7 nighly in it.
I know most of us are using the phone for everyday use, so most likely is using the "stable" CM7 as well.
I read that cm10 is almost good for everyday use by now, and it's time to upgrade.
Somebody could do me this favour, I promise to thank...
just reboot into recovery and wipe data and chache, if u want wipe battery stats also and it's done. simply install it like all custom roms.
0. Go to recovery
1. Make a Nandroid backup (recommended)
2. Wipe data, cache and dalvik
3. Install non-2ndboot CM10 (MB525 for Defy or MB526 for Defy+ or red lense Defy with Gingerbread kernel)
4. Reboot to stable recovery
5. Wipe data, cache and dalvik
6. Install latest 2ndboot CM10 build (one build for MB525 and MB526)
7. Install Gapps
8. Wipe cache and dalvik
9. Reboot
nastys said:
0. Go to recovery
1. Make a Nandroid backup (recommended)
2. Wipe data, cache and dalvik
3. Install non-2ndboot CM10 (MB525 for Defy or MB526 for Defy+ or red lense Defy with Gingerbread kernel)
4. Reboot to stable recovery
5. Wipe data, cache and dalvik
6. Install latest 2ndboot CM10 build (one build for MB525 and MB526)
7. Install Gapps
8. Wipe cache and dalvik
9. Reboot
Click to expand...
Click to collapse
hi nasty and thanks for the complete answer.
I read somewhere that the 'old' non 2ndboot cm10 doesn't contains the kernel, it is true or not?
If yes do i need to flash actually only the kernel or the complete 'old' rom?
tks
nastys said:
0. Go to recovery
1. Make a Nandroid backup (recommended)
2. Wipe data, cache and dalvik
3. Install non-2ndboot CM10 (MB525 for Defy or MB526 for Defy+ or red lense Defy with Gingerbread kernel)
4. Reboot to stable recovery
5. Wipe data, cache and dalvik
6. Install latest 2ndboot CM10 build (one build for MB525 and MB526)
7. Install Gapps
8. Wipe cache and dalvik
9. Reboot
Click to expand...
Click to collapse
Why those steps ? They are not necessary !
As already mentioned the steps above me are not necessary and for your question
The kernel is included in the Rom simply choose the latest nightly, BUT sometimes Quarx makes some Kernel Updates for a specific nightly then this is only a Kernel Update but atm there are no Kernel Updates so its not necessary
Alka-Seltzer PLUS said:
Why those steps ? They are not necessary !
Click to expand...
Click to collapse
It is safer to update from a CM10 ROM.
f0ster52 said:
hi nasty and thanks for the complete answer.
I read somewhere that the 'old' non 2ndboot cm10 doesn't contains the kernel, it is true or not?
If yes do i need to flash actually only the kernel or the complete 'old' rom?
tks
Click to expand...
Click to collapse
Only 2ndboot ROMs contain custom kernel. You can install 2ndboot CM10 directly, but it is safer to install from CM10 Stable Recovery.
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.