It's about time I upgraded

[Guest TylerDurdenK]

I'm currently running the standard Kernel, the advent ROM from 6th December 2010 with the MoDaCo custom ROM add-on and R5 Performance Pack.

Now I understand there have been significant updates lately so I am keen to get fully up to date.

I would like to know what order I should be installing things in order to get the best performance, and hopefully no BSoD that I have suffered from before.

Thanks in advance.

[Guest trevor432990]

I'm currently running the standard Kernel, the advent ROM from 6th December 2010 with the MoDaCo custom ROM add-on and R5 Performance Pack.

Now I understand there have been significant updates lately so I am keen to get fully up to date.

I would like to know what order I should be installing things in order to get the best performance, and hopefully no BSoD that I have suffered from before.

Thanks in advance.

A very good question Tyler and one I've been thinking about myself it would be very nice if Paul or one of his colleagues pinned a topic which explains how you update from earlier releases to the latest (stable) version. If it involves CWM I'd need to be convinced any issues with it have been resolved too. ;)

[Guest TylerDurdenK]

Looking in the pinned CWM topic people are reporting that ROM>CWM>MCR avoids the BSoD. But no mention of the MCK.

[Guest wobblydoggy]

Looking in the pinned CWM topic people are reporting that ROM>CWM>MCR avoids the BSoD. But no mention of the MCK.

No need for CWM unless you want to do a nandroid backup

Updating will delete all your current apps and system settings

Your app purchases are backed up on your google account

The order I regularly use when reinstalling after messing around.

Turn Vega completely off by pressing power switch for 8 seconds

Plug the charger into the vega

Install recovery drivers on computer

hold back button down for two seconds/whilst holding back button down press power for 2 seconds/let go of power and continue holding back button for 2 seconds

APX should now be found by your computer as a device

Install 1.08 off myadventvega.co.uk (instructions also available on there)

reboot

then install r6 and performance pack whilst usb debugging is enabled

then whilst usb is still in debugging, push paul's kernel files to your vega (as per instructions on the thread http://android.modaco.com/content/advent-v...e-advent-vega/)

reboot

Download flash 10.1 off the market

when this is done all is updated,

happy days

Edited February 1, 2011 by wobblydoggy

[Guest stevesilk51]

Wobbly,

Have you the link for the thread

"then whilst usb is still in debugging, push paul's kernel files to your vega (as per instructions on the thread)"

Thanks

Steve

[Guest wobblydoggy]

Wobbly,

Have you the link for the thread

"then whilst usb is still in debugging, push paul's kernel files to your vega (as per instructions on the thread)"

Thanks

Steve

http://android.modaco.com/content/advent-v...he-advent-vega/

Its on the sticky on the main page of the vega forum

[Guest TylerDurdenK]

Thanks for the advice.

What about if I do want Nandroid Backup, and the other things that CWM allows me to do?

[Guest stevesilk51]

http://android.modaco.com/content/advent-v...he-advent-vega/

Its on the sticky on the main page of the vega forum

Thanks Wobbly, didn't look closely enough!

[Guest wobblydoggy]

Thanks for the advice.

What about if I do want Nandroid Backup, and the other things that CWM allows me to do?

You can do them quite easily it really is straight forward.

with USB debugging on

The r6 pack comes with recovery installed, BUT dont click this app until you have visited http://android.modaco.com/content/advent-v...he-advent-vega/

When you are on this thread download THIS

You should search your computer for your adb.exe and extract the downloaded zip files in the same folder as this is located.

Then run cmd.exe from your start menu and type "cd C:\XXXXX\xxx\xxxx" in the command prompt where the xxx's are your folder location of adb.exe

once you have done that there should be a new line like C:\XXXX\xxx\xxxx>" (this should be the folder where adb is located) you can check that your device is attached by first typing "adb devices" which should list your device. If it does so, then move on to the commands listed below and follow them. Once these have transferred (it should tell you that xxxkb's have transferred) then you can now click the recovery app and it will boot into Clockwork mod recovery

You will have to do this everytime you uninstall 1.08 as this deletes the copied files as far as i know (but you shouldnt be deleting it that often, only if you mess around with it a lot, but if you have a nandroid backup it will restore to the exact position that you backed it up in app's and all)

adb push recovery.img /data/local/

adb push flash_image /data/local/

adb shell chmod 4755 /data/local/flash_image

adb shell /data/local/flash_image recovery /data/local/recovery.img

for example

My adb is located in C:\ANDROID\sdk\tools

so in cmd.exe I would type "cd C:\ANDROID\sdk\tools"

then I would extract the zipped files to C:\ANDROID\sdk\tools so both the recovery.img and flash_image would be in the exact same folder as my adb.exe which makes things much simpler in cmd.

then i would run the above commands (in the code box)

Edited June 6, 2011 by wobblydoggy

[Guest TylerDurdenK]

Whilst I really appreciate the effort you have gone to provide this info, I do know how to do these things as I have done them before, I am more interested in the order I should do them.

After suffering the BSoD that has occurred after applying CWM in the past I am hopeful to avoid this happening again.

[Guest wobblydoggy]

Whilst I really appreciate the effort you have gone to provide this info, I do know how to do these things as I have done them before, I am more interested in the order I should do them.

After suffering the BSoD that has occurred after applying CWM in the past I am hopeful to avoid this happening again.

If you do them in this order then you shouldnt get BSOD. Once you have a nandroid backup BSOD is really nothing to worry about at all because you can restore everything you had to just the way you had it.

I followed the steps above and CWM has worked 100% of the times i have tried it. (though that does not guarantee it will be the same for you, this is just what i did)

p.s i'm sure you have, but if we're going to make a topic about it, I may aswell simplify as much as possible to avoid other people asking.

The only time i get BSoD is when I don't flash the utility before running the recovery.apk

Edited February 1, 2011 by wobblydoggy

[Guest TylerDurdenK]

Cool.

FWIW I am taking the advice of someone in the CWM thread and installing in this order:

Advent Stock ROM >> ClockWorkMod >> MoDaCo Custom Add-On >> MoDaCo Custom Kernel

[Guest wobblydoggy]

Cool.

FWIW I am taking the advice of someone in the CWM thread and installing in this order:

Advent Stock ROM >> ClockWorkMod >> MoDaCo Custom Add-On >> MoDaCo Custom Kernel

That would also work fine, just means you have to download and install the recovery.apk which is already pre-installed in modaco rom. ;)

[Guest Mogedwards]

I have been wondering when I should do the next upgrade but I am waiting for Advent to release the final version with Flash. Surely this is due anytime now,

I am asuming this is still the case or have I missed something. If it is still the case, is there any point messing just yet?

[Guest HunteronX]

Cool.

FWIW I am taking the advice of someone in the CWM thread and installing in this order:

Advent Stock ROM >> ClockWorkMod >> MoDaCo Custom Add-On >> MoDaCo Custom Kernel

Flash the new MoDaCo Custom Kernel, as this seems to be the real solution to BSOD's.

[Guest emergant]

Flash the new MoDaCo Custom Kernel, as this seems to be the real solution to BSOD's.

Yes flash the kernel as soon as you can after running nvflash (nvflash from the vega roms formats the device anyway). The new Kernel leaves the misc partition unmounted as it was becoming corrupted causing BSOD. I have proved this to my satisfaction by running a format of just that partition to recover from a BSOD.

Now why it became corrupted and whether anything else may become corrupted I have no idea.