231 replies to this topic

[TerryH]

thanks for the confirmation, don't want to test some images if i am not shure that the restore. doesn't work 100%  

[emergant]

I can confirm that BSOD is caused by corruption of the misc partition as stated elsewhere.  I just fixed a BSOD by formatting only that partition using nvflash.  I have no idea what the misc partition is used for but not mounting it would be a good idea I think in Pauls future ROMs if its not needed.  Actually could we delete it altogether?  

I am running the new kernel and CWM and caused the BSOD by using the USB switcher

[rpmccormick]

emergant, on Jan 29 2011, 08:35, said:

I can confirm that BSOD is caused by corruption of the misc partition as stated elsewhere.  I just fixed a BSOD by formatting only that partition using nvflash.  I have no idea what the misc partition is used for but not mounting it would be a good idea I think in Pauls future ROMs if its not needed.  Actually could we delete it altogether?  

I am running the new kernel and CWM and caused the BSOD by using the USB switcher

Can you please post instructions for "formating only the misc partition using nvflash"?  If some one could just make a .exe that you run which fixes the BSOD without changing anything else, I'm sure a lot of people would use and appreciate it.

[simonta]

Don't ask me why

Several people, me included, have fixed BSODs by installing in this order ROM->CWM->mcr

I used to do ROM->mcr->CWM and got BSODs

[emergant]

rpmccormick, on Jan 30 2011, 05:17, said:

Can you please post instructions for "formating only the misc partition using nvflash"?  If some one could just make a .exe that you run which fixes the BSOD without changing anything else, I'm sure a lot of people would use and appreciate it.

AT YOUR OWN RISK ETC

Well the 1.065 rom uses this command line

nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x000c0075 --create --go

to flash the whole rom

I did this from a linux vm on a mac on which I'd renamed the bct file

nvflash -w --bct flash.bct --bl bootloader.bin --format-partition 5

comparing those lines, from a 1.06 rom directory I'd run:

nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --bl bootloader.bin --format-partition 5

You should run this after extracting the vega rom zip and changing to that directory.  Partition 5 should be misc or msc as the vega rom calls it.  You can get this info from the flash.cfg file.  The --bct  part may not be needed.  Not sure

This is definitely vega rom specific dont use it on anything else which may have a different partition structure.   Worked for me

If anyone has the tools to edit the self extracting zip file it should be simple enough to change the batch file to do this automatically

Edited by emergant, 30 January 2011 - 06:52 PM.

[newbe5]

Apologies if this has already been answered, but i am using MCR6 on 1.06.5 and this comes built in, but when i try to use it, the vega reboots then comes up with the recovery icon in the center of the screen with a process bar that quickly dissapears, then the recovery icon image just stays in the center of the screen and nothing else happens, any way around this?

[rvdgeer]

newbe5, on Jan 30 2011, 20:58, said:

Apologies if this has already been answered, but i am using MCR6 on 1.06.5 and this comes built in, but when i try to use it, the vega reboots then comes up with the recovery icon in the center of the screen with a process bar that quickly dissapears, then the recovery icon image just stays in the center of the screen and nothing else happens, any way around this?

Clockworkmod is NOT built in...
Only the apk to boot to it is built in...
You need to flash cwm yourself to be able to use it!

[Thresherinc]

olionair, on Jan 26 2011, 18:09, said:

you not keep a nandroid back up?

Didn't see a point until I got CWM properly installed.

[thedicemaster]

emergant, on Jan 30 2011, 20:49, said:

comparing those lines, from a 1.06 rom directory I'd run:

nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --bl bootloader.bin --format-partition 5

i don't know if the linux version of nvflash is different, but on windows that would be:

nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --bl bootloader.bin --format_partition 5

on windows nvflash doesn't accept --format-partition

[emergant]

thedicemaster, on Feb 2 2011, 18:36, said:

i don't know if the linux version of nvflash is different, but on windows that would be:

nvflash.exe --bct H5PS1G83EFR-S6C_V24_0625.bct --bl bootloader.bin --format_partition 5

on windows nvflash doesn't accept --format-partition

Sorry you're right on both windows and Linux.  Its a typo as I cant copy/paste between my linux vm and macos.   On linux running nvflash without arguments documents the syntax

[67Mustang]

emergant, on Feb 2 2011, 19:16, said:

Sorry you're right on both windows and Linux.  Its a typo as I cant copy/paste between my linux vm and macos.   On linux running nvflash without arguments documents the syntax

Has anyone had any problems in extracting/ unzipping the first file required for CWM?  I've tried this with both WinZip and WinRar, and it comes up with an error message saying 'file is unknown format or damaged' (I'm using a Windows XP machine if that makes any difference).

Is there something obvious I'm missing here?

[simonta]

67Mustang, on Feb 3 2011, 19:29, said:

Has anyone had any problems in extracting/ unzipping the first file required for CWM?  I've tried this with both WinZip and WinRar, and it comes up with an error message saying 'file is unknown format or damaged' (I'm using a Windows XP machine if that makes any difference).

Is there something obvious I'm missing here?

Download again?

[67Mustang]

I've tried downloading and unzipping it 8 or 9 times (the download is fine) with both WinZip and WinRar on two different PCs, but each time I get the same error message (seems a bit futile to just keep on downloading the same file over and over).

I was able to unzip the MCR r6 files with no problems (to get the ADB drivers, which installed without a problem), so it just seems to be the first CWM zip file that is causing the problem (although haven't tried the reboot download yet).

I tired it again this morning at work, but unfortunately the download website is getting blocked, so I'll need to wait until later tonight to try it again, although I'd be amazed if I'm the only person who has experienced this problem.

Worst case scenario, I'll try downloading and installing MCR r7 from my PC without having CWM, which I guess is not too big a deal, but would like to figure out why the CWM files won't unzip if possible.

[Dunetails]

67Mustang, on Feb 4 2011, 09:22, said:

I've tried downloading and unzipping it 8 or 9 times (the download is fine) with both WinZip and WinRar on two different PCs, but each time I get the same error message (seems a bit futile to just keep on downloading the same file over and over).

I was able to unzip the MCR r6 files with no problems (to get the ADB drivers, which installed without a problem), so it just seems to be the first CWM zip file that is causing the problem (although haven't tried the reboot download yet).

I tired it again this morning at work, but unfortunately the download website is getting blocked, so I'll need to wait until later tonight to try it again, although I'd be amazed if I'm the only person who has experienced this problem.

Worst case scenario, I'll try downloading and installing MCR r7 from my PC without having CWM, which I guess is not too big a deal, but would like to figure out why the CWM files won't unzip if possible.

It's not just you, I'm also having problems opening the zip.  There's something wrong with the download.

I'm using the built in Ubuntu zip handler.

[ho66es]

i downloaded it twice today, 1st time was very slow and corrupt when trying to open. Second time was fine. I wonder if the load balancing feeds from more than 1 file server in which case maybe one has a corrupt zip?

[rferrett]

So out of iinterest does anyone know if the issues Paul reported around rom manager have been resoolved? Or is it still incompatible with the Vega?

[Sir Gash]

rferrett, on Feb 8 2011, 11:02, said:

So out of iinterest does anyone know if the issues Paul reported around rom manager have been resoolved? Or is it still incompatible with the Vega?

What issues? I think there may have been a problem with the Reboot into Recovery option (don't really use this myself), it's not that important really as you can use Paul's app instead. I use Rom Manager regularly to do nandroid backups/restores and it works perfectly.

[bennji_boy]

Paul, on Nov 29 2010, 16:40, said:

To install the recovery image and flash utility, extract the first zip file to a directory, then enter the following (this assumes you have 'adb' on your machine):

Stupid question alert, how do I know if I've got ADB on my machine? I don't think I have because when I put the first command in I got a not recognised message.

I did install R6 using ADB drivers or something (I can't really remember it seems that long ago now) and now when I plug the Vega it comes up as android ADB device in device manager.

What do I need to do to get this to work?

Final stupid question, I'm right in saying that if I install CWM it means I can install future ROMs (including R8) without going near my PC?

If so, Amen to that brother!

Edited by bennji_boy, 10 February 2011 - 04:23 PM.

[jimh]

There is a very good thread about this here  
I managed to follow it & get CWM installed so it must be good because I'm very new to all this.

Thread

[simonta]

bennji_boy, on Feb 10 2011, 14:05, said:

Stupid question alert, how do I know if I've got ADB on my machine? I don't think I have because when I put the first command in I got a not recognised message.

I did install R6 using ADB drivers or something (I can't really remember it seems that long ago now) and now when I plug the Vega it comes up as android ADB device in device manager.

What do I need to do to get this to work?

Final stupid question, I'm right in saying that if I install CWM it means I can install future ROMs (including R8) without going near my PC?

If so, Amen to that brother!

When Paul ships his packs, he includes adb.exe but renames it to adb-windows as the pack includes adb for Mac and Linux - so just run adb-windows instead of adb.  It will make things much easier if you have adb-windows on the path.  If you know how to do this, great.  If not, copy adb-windows.exe to c:\windows.  You may as well rename it to adb.exe as well.  Easier to remember and type!

Cheers