Mtk Nvram Editor.rar

[Martta Borromeo]

Theversion of BIOS I have is 0511, which is the 2nd oldest available to download from the ASUS site. Other people running into this error have been downgrading the BIOS. I don't have the option of flashback unfortunately. Any way around this BIOS lock?

Do I update to 2403 standard BIOS first using a standard bios update method in the bios, then boot windows and run the sce, send you the file to kindly modify, then use sce to place your modified bios back, then I need to use pmpatch to patch bios 2403, then use ftk to flash this modified bios back?

Just as a backup, when I update my Bios to 2403 and extract nvram.txt, I would like to send it to you so you could correctly edit it, if you kindly could, in the meantime could I install AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext somehow so I could continue to use my Mavericks 10.9.2, or if something goes wrong and I am stuck on a non patched Bios?

Actually, what would be easier for me is to do is run scewin on my current patched 2203 bios and send you the nvram.txt file for editing, scewin it back to the board, so I have an unlocked patched 2203, then just pmpatch a patched 2403 bios to the board. Would this work, as this wont impede on my workflow.

lightServer, that makes sense, so could I just run scewin on my current patched 2203 bios and send you the nvram.txt file for editing, scewin it back to the board, so I have an unlocked patched 2203, then just pmpatch a patched 2403 bios to the board. Would this work, as this wont impede on my workflow?

Ahh, maybe I have misunderstood. I want to goto 2403 patched Bios, but can't as my current patched bios 2303, is protected. So if I flash the nvram.txt file back with SCEWin, I can then flash my Bios suing FTK with a PMPatched 2403 Bios? Or have I misunderstood?

I am sorry, the this Asus P8Z77-V LX is one I use constantly in production, so this is why I am being cautious, the second I upgrade the Bios to 2403 standard I will not be able to boot Mavericks 10.9.3, so want to be 100% sure I can quickly get it back up and running with a patched 2403.

So if I upgrade to 2403 standard boot to windows, dump the nvram.txt, end it to you for edit, you send it back, the next section I am sorry, but am still not sure about, could be please be very simple explanation step by step please, I would be very grateful.

The command above copies the second-test-config.cfg file in the root of the flash to the configs folder on the flash drive. Cisco IOS asks for the destination file name (which I already supplied) so you only have to hit enter for these questions.

You have now seen how to move around the Cisco IOS filesystem, how to create folders, copy files and create/extract TAR files. If you want to know how to copy files between your local router / switch and an external server like a TFTP server, take a look at the following lesson: How to upgrade the Cisco IOS image.

In most cases, the file system used is fat32. This can be seen from the fact that most cisco IOS platforms have the fsck utility which is a FAT filesystem check. Also, most USB flash drives that are used as external storage ports on cisco devices are recommended to be formated as fat32.

Some cisco platforms have the ability to change file systems as well. Depending on the platform, using the IOS command filesystem filesystem-type you are able to format any file system (flash, nvram or usb flash drive) on a Cisco device to fat16, fat32 or qnx4.

It is true that the startup-config is saved within NVRAM. When a Cisco device boots up, it will look in the NVRAM and it will search for the file named startup-config and it will load it into RAM as the running-config. However, it is possible, and it is common practice, to have several configurations saved within a device. These are not active but are saved as files of different names. These files can be saved in NVRAM or flash. They are simply being stored.

In my experience, the wifi is pretty solid and I'd really like to see some comparisons with stock and/or immortalwrt. Do they comply with regulations? Since both are for china mainland usage and china allows for at least 3 more dbm in UNII2 and 3 which essentially is double the power (200mw vs 400mw in unii2 and 400mw vs 1000mw in unii3)

You can get these numbers in openwrt if you set your country to China but then you are breaking the law.

From Luci I decided to do a reset just to be sure. The router didn't come back up.

I connected UART, and noticed that the boot menu gives options to start from firmware0 firmware1, and "firmware selected by Xiaoqiang".

The default is the latter, which dies ouit due to (I believe it was) bad checksum. firmware1 doesn't load either (I believe it's the same error, leading me to believe they point to the same), firmware0 loads correctly.

I'm positive that I did something wrong, but it also feels like there's something missing in the instructions. e.g.: Is there a flag that says which is the active stock firmware partition based on which the other should be flashed? Or something along those lines?

The instructions still need some "refining" and updating on the wiki, which will no doubt come as things progress, the unit becomes more popular and the RB03 changes get merged into the master snapshot.

Not with the latest images, you'll definitely kill it. Basically, writing the first factory.bin overwrites the last several partitions and makes 2 new ones - kernel and overlay. If you do the second write, it'll write in place of the overlay partition and corrupt it.

You do need the nvram set "boot_fw1=run boot_rd_img;bootm". I'm not sure why it is commented out. (Maybe the instructions still refer to an older image layout). If it is not set, the boot system will not be able to boot openwrt. You'll either need to recover to stock or connect to uart to manually select the partition to boot.

To reiterate dekomote's message... Do not do mtd write on firmware1 with the latest images. If you've read the entire thread, you'll see I had some specific issues. I think it was writing to firmware1 that actually caused my issues.

As with any flashing activity, be prepared to recover to stock either using the xiaomi recovery tool or setting up a tftp server. Mikeeq's recovery instructions should work. I found recovery to stock very reliable. As long as you are only touching the firmware partition and nothing else, recovery should work.

So basically I flashed firmware partition, it didn't update the partitions as it didn't boot from it. I flashed both firmware and firmware1 (no reboot in between), at which point it did start openwrt's factory flash, which repartitioned the layout, removing firmware and firmware1.

Yes, but if you have a real arcade, you must somehow edit the file "ea3-config.xml". Maybe connecting the hard drive with the dongle to PC will decrypt it, but yes, there are apps that can emulate a eamusement server. (eg. eaLocalServer.exe).

I tried to run the festo using the Spice tool, but the execution only appears in the command window and the window closes.

First of all, the process that I've executed

1. Uncompress festo

2. Creating dev/nvram

3. Copy all files from prop/defaults to dev/nvram.

4. Run spicecfg to create key bindings, card numbers, and change e-amusement emulation from options to enable

5. Run as spice.

If I'm wrong, point it out. If I did it right,

I will attach the log file, can anyone help me?

3a8082e126