Want to make sure I've got the procedure down. I'm currently running the latest stock rooted (but not unlocked).
Let me know if this plan looks right or if you see problems or have recommendations...
Edit: Included two wipes as per Joker's instructions
1) Backup apps and data
2) Unlock
3) Install romracer's latest CWM (http://forum.xda-developers.com/showpost.php?p=16654262&postcount=1)
4) Make backup (or two)
5) Boot into recovery
6) Go to Mounts + Storage -> Format system
7) After format, Wipe data / factory reset
8) Install CM9
9) Wipe data / factory reset again
10) Install CM9
11) Install gapps
12) reboot
Did I miss anything?
Should I then install the latest 1.40 OC kernel? Edit: Looks like no, custom kernel built in. Thanks roundeye
Last I knew, jokers cm9 had an oc kernal with it, but in either case don't install a blur/cm7 kernal on cm9.
As for your steps, double check the first post in jokers cm9 thread because I believe you have to flash twice or something along those lines to get cm9 set up properly with its installer/backup scripts. Otherwise looks good.
Sent from my 1.3 OC'd CM7.2 Electrify.
roundeye1987 said:
As for your steps, double check the first post in jokers cm9 thread because I believe you have to flash twice or something along those lines to get cm9 set up properly with its installer/backup scripts. Otherwise looks good.
Click to expand...
Click to collapse
Awesome thanks... I did see something about flashing twice. On his post, he lists the steps as:
WIPE
then flash
wont boot
wipe and flash again.
also wipe between versions.
did i mention to wipe
Click to expand...
Click to collapse
So I guess I go all the way through step 8, then repeat steps 7 and 8 again? then do 9 and 10?
Here's Joker's explanation for needing two wipes:
there are scripts built into cm9 that copy certain gapps over to cache and then restores them to system. if you are coming from gingerbread this messes a few things up. so to fix we wipe system, data, and cache so the script cant work the first time around. then we wipe and flash again letting the script work.
Click to expand...
Click to collapse
Don't do what I did: Forgo unlocking, and flash gapps and cm9 at the same time
Haha I'll keep that in mind
Ouch! That must have been harsh. Did you SBF back then?
Dev Named Josh said:
Don't do what I did: Forgo unlocking, and flash gapps and cm9 at the same time
Click to expand...
Click to collapse
Related
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the two files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?) Now DON'T reboot before you made the next step, cause you have to start from zero if you reboot before making the next step
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
9Lukas5 said:
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?)
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
Click to expand...
Click to collapse
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
where can i download FreeXperiaRecovery?? I will tray this!
avez197 said:
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
Click to expand...
Click to collapse
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
9Lukas5 said:
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
Click to expand...
Click to collapse
Thanks. Will give feedback after trying
barsom said:
where can i download FreeXperiaRecovery?? I will tray this!
Click to expand...
Click to collapse
If you download Flashtool 0.2.9.1 there is FreeXperiaRecovery included. Look into the list, there wrote to click on the xrecovery button for installing FreeXperiaRecovery. The files are included in flashtool.
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
nadiros said:
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
Click to expand...
Click to collapse
Yes i ment this.............maybe you're right, cause it will be formatted by installing the rom, too.........hm..will correct op.
Edit: I made it that way always, and had never problems, so i haven't thought about it.
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Hello 9lukas5,
I thought I might mention that I've finally managed to fix my wlod but by installing setcpu on the earlier version of J's rom I was using, and setting it up to on boot run the processor at the usual 998 speed. Then I flashed the update.zip (from j's latest release, just formats the system) which didn't remove setcpu so the cpu was running at 998, this stopped all the random reboots and wlods.
I tried for a couple of weeks to use an update, trying so many different ways of stopping my phone being unusable as soon as I flashed the updates due to wlods.
Just though I'd mention it in this thread as it was on topic. Not everyones fix I'm sure, but helped me.
Cheers for all your support and help with installing the roms.
Sent from my X10 using XDA App
BULL3TPR00F said:
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Click to expand...
Click to collapse
K - Right on, ty. Just so it's out there and people know ;-)
I believe the majority of WLODs are to due with the CPU constantly running at full speed.
I was getting a lot of WLODs with FreeXperia Kernel-10 on my ROM until I manually set the CPU governor to on demand.
Just go into Cyanogen Settings and change the CPU governor to on demand (it probably already is set to on demand, so change it to something else and then change it back to on demand).
After that my CPU was running at more than the max frequency and I haven't had many WLOD's (think I've had one since, a major improvement).
Erm not to be funny but their are no WLOD due to the changes J has made in his new version, regardless of how I flash it, no WLOD anymore... It has nothing to do with the way you flash the rom that caused this...
Hi guys,
I have follow ALL step from the step 1.
The phone boot, ask for the PIN code, then the page to change the language and then WLOD...
Do you think it come from the CPU frequency ?
I can't found the BTS kernel for this ROM.
Thank you for your help.
hmm....I shared it cause I hadn't any problems of WLODs yet on Cm7 since J019
Hello all,
the main trouble I had causing wlod, was definitely the clock speed. When I flashed the rom (about twenty times, different ways) I would not get enough time to configure any cpu settings, or any other settings, before my phone crashed and it would just start to bootloop with wlod.
I had to install setcpu on an older version of j's rom which didn't have overclock. Checked the box to apply settings on boot. So that when I flashed j's latest rom which is just the update of the system, all my apps were there (didn't bother wiping cache, data, etc) setcpu was still running on boot to keep the cpu set to 998.
Haven't had a single problem since, apart from low battery phone crash.
I tried so many different ways to flash before trying this, hope this helps someone.
Sent from my X10 using XDA App
Any body make a stock kernel image to flash to check sleep state vrs miniloader issue?????????
Worked a treat!! Thank you!
So, I've been trying to install the Cyanogenmod for 2 days without success...
This is what I've been doing. Tell me if I do something wrong...
-Start with stock KE2
-Flash CF-Root wich also contains CWM
-Factory reset / Cache wipe
-Put cyanogenmod .zip on the phone
-Boot into recovery
-Select install .zip from sdcard, and I select the zip
-Phone says install succesfull (the install just takes like 3 seconds, is it normal?)
-I go back to the previous menu and select reboot phone
It gets stuck at the black "samsung galaxy s2" screen. I left it for more than 20 minutes that way. Nothing happens.
I just power it off and re-flash a stock firmare via odin...........
This happens with both the stable and the nightly cyanogen mod builds.
Could you help me please?
1) boot into CWM recovery
2) Flash CM7 zip
3) reboot into recovery again
4) flash CM7 zip again
5) wipe data/cache/dalvik cache (you will lose all your app data, but not pictures/media/etc)
6) reboot and wait for it to boot, upto 10min.
Why dont you just flash and cf- root stock rom then thru cwm just install the rom? easy and works, atleast for me it did, got back to stock thu , its better after you freeze all bloatware..
hope it helps
Sent from my GT-I9100
veyka said:
1) boot into CWM recovery
2) Flash CM7 zip
3) reboot into recovery again
4) flash CM7 zip again
5) wipe data/cache/dalvik cache (you will lose all your app data, but not pictures/media/etc)
6) reboot and wait for it to boot, upto 10min.
Click to expand...
Click to collapse
I'll try that. But why flash it 2 times?
maxolina said:
I'll try that. But why flash it 2 times?
Click to expand...
Click to collapse
So it works? Dunno, it was something todo with differences in the CF-root CWM recovery and the CM7 CWM recovery and busybox.
If you'd bother to read the instructions for flashing CM (which you clearly didn't, else you wouldn't be asking this question), they're pretty clear about the requirement to flash the rom twice. The why is irrelevant. The simple reality is in order for it to function it needs to be flashed twice.
If you haven't already, do yourself a favour and flash the original stock firmware that was on the phone when you bought it before you end up trashing it :-/
maxolina said:
I'll try that. But why flash it 2 times?
Click to expand...
Click to collapse
veyka said:
So it works? Dunno, it was something todo with differences in the CF-root CWM recovery and the CM7 CWM recovery and busybox.
Click to expand...
Click to collapse
It worked! You are my favourite person on the world right now!
maxolina said:
It worked! You are my favourite person on the world right now!
Click to expand...
Click to collapse
Glad you got it working
maxolina said:
It worked! You are my favourite person on the world right now!
Click to expand...
Click to collapse
You wouldn't have actually needed his advice if you bothered to read the instructions at least twice... -.-
so i searched the boards and all i found were people having trouble with CM7... not CM9...
so it seemed like i flashed CM9 and gapps on it seemlessly... i rebooted excited that i was going to see ics... but it's just stuck there... the red M, dual core with unlocked at the top of the screen..... no matter how many times i remove the battery and how long i wait there.. it's just sits there...
Any help? I'm a major noob when it comes to flashing and stuff... like i learned all this today and decided to try it out...
phone is atrix 4g with att.... used clockwordmod and basically followed directions off this site
www . stuff4android . com/2012/02/10/upgrade-motorola-atrix-4g-to-android-4-0-3-ics-via-cyanogenmod-9/
any help would be appreciated!
Titaneers said:
so i searched the boards and all i found were people having trouble with CM7... not CM9...
so it seemed like i flashed CM9 and gapps on it seemlessly... i rebooted excited that i was going to see ics... but it's just stuck there... the red M, dual core with unlocked at the top of the screen..... no matter how many times i remove the battery and how long i wait there.. it's just sits there...
Any help? I'm a major noob when it comes to flashing and stuff... like i learned all this today and decided to try it out...
phone is atrix 4g with att.... used clockwordmod and basically followed directions off this site
www . stuff4android . com/2012/02/10/upgrade-motorola-atrix-4g-to-android-4-0-3-ics-via-cyanogenmod-9/
any help would be appreciated!
Click to expand...
Click to collapse
You need to flash CM9, let the phone boot completely, let the phone sit for 10 minutes to build system files, then reboot and flash GAPPS. You can't/shouldn't flash a CM ROM and GAPPS together. Always flash the ROM, reboot, then flash GAPPS.
Also, did you perform a full fastboot wipe prior to flashing?
I don't think it is necessarily required to boot once before flashing Gapps. I have always flashed Gapps right after flashing the ROM (without booting in between) and it also instructs on the CM Wiki page (for the Atrix) to flash Gapps after flashing the ROM:
7. Select Install zip from sdcard.
8. Select Choose zip from sdcard.
9. Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Motorola Atrix 4G should now boot into CyanogenMod.
Source:
http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
Last updated 2/8/12
Also, when using Rom Manager it gives the option to flash Gapps in the same recovery session as well.
Note: Of course, I speaking solely on CM7 and not CM9. And I'm not trying to say your method is wrong either. I have noticed that there are CM-based ROMs that do recommend separate recovery sessions for flashing additional packages so I don't disagree with you.
CaelanT said:
You need to flash CM9, let the phone boot completely, let the phone sit for 10 minutes to build system files, then reboot and flash GAPPS. You can't/shouldn't flash a CM ROM and GAPPS together. Always flash the ROM, reboot, then flash GAPPS.
Also, did you perform a full fastboot wipe prior to flashing?
Click to expand...
Click to collapse
live4nyy said:
I don't think it is necessarily required to boot once before flashing Gapps. I have always flashed Gapps right after flashing the ROM (without booting in between) and it also instructs on the CM Wiki page (for the Atrix) to flash Gapps after flashing the ROM:
7. Select Install zip from sdcard.
8. Select Choose zip from sdcard.
9. Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Motorola Atrix 4G should now boot into CyanogenMod.
Source:
http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
Last updated 2/8/12
Also, when using Rom Manager it gives the option to flash Gapps in the same recovery session as well.
Note: Of course, I speaking solely on CM7 and not CM9. And I'm not trying to say your method is wrong either. I have noticed that there are CM-based ROMs that do recommend separate recovery sessions for flashing additional packages so I don't disagree with you.
Click to expand...
Click to collapse
While I would agree that it is possible to flash any number of files at the same time before rebooting, I would argue at the same time that it is not good practice to do so. I would also argue that because a wiki, or even Cyanogen himself says this is fine, nobody can know for sure if doing this can in fact cause issues. It's something I run into at work all the time. "Just because something is done using a particular method, this does not mean it is the only or best method". Things happen which you cannot foresee such as file versions overwriting other different file versions which could have undesirable results after booting. Some of these results may not be seen on the surface, but could be the root cause of such things as, lets say for example, high battery usage at idle.
So, while I agree with you in part, we shall have to agree to disagree. My usual method for any ROM would be the following:
FULL fastboot wipe
Reboot to recovery
Flash ROM
Reboot and let phone sit for 10 minutes after full boot up
Reboot to recovery
Wipe Dalvik and cache
Flash GAPPS (if ROM requires it)
Reboot and set up accounts
Reboot to recovery
Wipe Dalvik and cache
Flash chosen kernel
Reboot and set CPU clock, voltage, etc.
Done.
Actually, I do agree with you. The only part I didn't agree with was the part where you said "can't" in regards to flashing CM and Gapps together. I probably wouldn't have said anything if you left it at "shouldn't". I agree that, for the most part, there is no single way to do things, which is why I mentioned it was possible and can work.
Please don't take my comment as an attempt to undermine you. You have provided great advice numerous times and is much appreciated. I actually bookmarked a post that you made awhile back detailing "fastboot wipes" that I now use every time I flash a new ROM. (I actually have the instructions mesmerized now but I still have the bookmark)
http://forum.xda-developers.com/showpost.php?p=17656035&postcount=5
CaelanT said:
While I would agree that it is possible to flash any number of files at the same time before rebooting, I would argue at the same time that it is not good practice to do so. I would also argue that because a wiki, or even Cyanogen himself says this is fine, nobody can know for sure if doing this can in fact cause issues. It's something I run into at work all the time. "Just because something is done using a particular method, this does not mean it is the only or best method". Things happen which you cannot foresee such as file versions overwriting other different file versions which could have undesirable results after booting. Some of these results may not be seen on the surface, but could be the root cause of such things as, lets say for example, high battery usage at idle.
So, while I agree with you in part, we shall have to agree to disagree. My usual method for any ROM would be the following:
FULL fastboot wipe
Reboot to recovery
Flash ROM
Reboot and let phone sit for 10 minutes after full boot up
Reboot to recovery
Wipe Dalvik and cache
Flash GAPPS (if ROM requires it)
Reboot and set up accounts
Reboot to recovery
Wipe Dalvik and cache
Flash chosen kernel
Reboot and set CPU clock, voltage, etc.
Done.
Click to expand...
Click to collapse
live4nyy said:
Actually, I do agree with you. The only part I didn't agree with was the part where you said "can't" in regards to flashing CM and Gapps together. I probably wouldn't have said anything if you left it at "shouldn't". I agree that, for the most part, there is no single way to do things, which is why I mentioned it was possible and can work.
[/url][/U]
Click to expand...
Click to collapse
I didn't take your comments as anything but constructive, so please don't get the wrong impression. I was simply continuing the discussion. When I used the word "can't" I also added the "/shouldn't" because the "can't" was more of a metaphor than a literal statement!
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
Make sure to use Joker's Clockworkmod recovery, named cwm-v3, here.
Thanks gollyzila, I am using the Jokersax CWMv3 recovery image at this time. I meant to mention that earlier in my first post.
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
try pulling the battery and then booting again. if that doesn't work flash 0.4.0 first like ccallahan suggested
CCallahan said:
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
Click to expand...
Click to collapse
wala! that worked. thank you very much CCallahan. much appreciated.
i was having the same problem heres what i did i factory reset cleared cache/dalvic installed 3.1 then reboot wipe cache/dalvic then i flashed 4.4 over it
when you first flash any cm9 fresh, not over a backup, you must flash twice. Joker has mentioned this many times that the scripts he has for the install have to run twice in order to fully install.
1. Flash cm9 (whatever beta you want)
2. Reboot recovery (in advanced in cwm)
3. Flash rom again
4. Flash gapps
5. Boot to system
You should be good to go now
sent from my Kick Ass MIUI MoPho using XDA premium
FXP said:
HOWTO
Install instructions:
1. Install a Recovery (there are some around this forum)
2. Flash Rom
3. Flash gapps
4. Wipe (only required 1st time)
5. Flash kernel (fastboot flash boot boot.img)
Click to expand...
Click to collapse
Hope I'm not making a fool out of myself..
But, why are the instructions in that order?
The normal way to go is:
Flash kernel > factory/cache partition/system/dalvik cache wipe > Install the ROM > Install any .zip (fixes, addons, apps) > Reboot.
Is there any specific reason why the steps mentioned by the OP are in this order?
Thank you!
hmnk said:
Hope I'm not making a fool out of myself..
But, why are the instructions in that order?
The normal way to go is:
Flash kernel > factory/cache partition/system/dalvik cache wipe > Install the ROM > Install any .zip (fixes, addons, apps) > Reboot.
Is there any specific reason why the steps mentioned by the OP are in this order?
Thank you!
Click to expand...
Click to collapse
Replace 1 with 5 and then install.
evilbarcode said:
Replace 1 with 5 and then install.
Click to expand...
Click to collapse
Aye aye..
BTW, just out of inquisitiveness, why did the OP mention the steps in that order?
hmnk said:
Aye aye..
BTW, just out of inquisitiveness, why did the OP mention the steps in that order?
Click to expand...
Click to collapse
Not too sure, I have a slight feeling they messed up when writing it all down. But kernel is always first. After kernel dont boot the rom, just power on and head to recovery. Full wipe, format system, install rom, install gapps, full wipe and wipe dalvik cache, then reboot and watch the magic.
evilbarcode said:
Not too sure, I have a slight feeling they messed up when writing it all down. But kernel is always first. After kernel dont boot the rom, just power on and head to recovery. Full wipe, format system, install rom, install gapps, full wipe and wipe dalvik cache, then reboot and watch the magic.
Click to expand...
Click to collapse
Haha ok..
CM9 was great itself, now lets see what CM10 has in store for me
evilbarcode said:
Not too sure, I have a slight feeling they messed up when writing it all down. But kernel is always first. After kernel dont boot the rom, just power on and head to recovery. Full wipe, format system, install rom, install gapps, full wipe and wipe dalvik cache, then reboot and watch the magic.
Click to expand...
Click to collapse
It doesn't matter, if you have recovery in previous ROM you can flash new ROM first in old reco and then flash kernel in fastboot.
May be the answer lies in here..
hmnk said:
Ok problem solved..
build.prop error means I have to use a Kernel that doesn't verify name in build.prop..
So I tried expeacer's MIUI Kernel(Extended stock kernel) and I was able to install CM10..
This info was courtesy of metalrawk
This could possibly be the reason why FXP instructed to flash the Kernel after ROM installation
Click to expand...
Click to collapse
evilbarcode said:
Replace 1 with 5 and then install.
Click to expand...
Click to collapse
that is the best way, it worked for me thanks a lot
tnx
Tnx it helped me too