@TMavica, did you get any of the kernels to boot, any at all?
or was the problem only with 2.6.32.61-plus kernel?
The best way to enter Open Mode is the back-to-back flashing.
If you do it the simple way, just flash Open Mode and then delete the aegis directories, you are going to have problems
People have checked this and it is indeed so, the device is going to be somewhat unstable, especially at boot.
@plourde, when you flash with "--flash-only=kernel" parameter, the flasher needs to get the APE algorithm from a firmware FIASCO image. That is why you need to specify the "-a firmware.bin" flag on the flasher command line.
Does ubiboot give any error messages with green text when you select a kernel for booting?
Can you do the following; flash back to the "normal kernel", for example using command:
"sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R"
Then, get the ubiboot log files (ubiboot.log, ubiboot.dmesg) from the configuration directory (/home/user/MyDocs/boot/)
Post the logs here and I will look what's the problem.
Nil kernel work. So what i need do? My way is normal mode > flash to open mode > del aegis dir, and do all things again?
According to Rainisto, the correct way to flash to open mode is to flash the device back-to-back, that way it should work best.
How to do it, You need to flash first to Closed mode, then to Open mode, without device booting between.
If you have Linux, you can give the flashing commands on the same command line, like this:
"sudo flasher -F firmware.bin -F emmc.bin -f -R ; sudo flasher -a firmware.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R"
If you have Windows, you can copy-paste the commands from a notepad or something to the console, giving the second command after the first has executed. Or you can have 2 DOS consoles open with the command written there and first press enter on the first, and when it has finished, on the second.
