View Single Post
Posts: 139 | Thanked: 176 times | Joined on Oct 2012
#1387
Originally Posted by peterleinchen View Post
For the next poor soul that tries (is described elsewhere as well),
with back-to-back is meant to do;
3.a flash device (firmware) in closed mode
do NOT boot up
3.b flash open-mode-kernel
Have fun!
This still eludes me, after doing 'disclaimer-cal remove View-openmode', how could i flash the device again without it restoring the warning message. Because that's what happend.

Finally, after removing the warning with 'disclaimer-cal remove View-openmode', i settled to not doing a full flash but just this:
Code:
./flasher64 -f -F main.bin  -F emmc.bin  --flash-only=mmc 
./flasher64 -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f
Then afterwards, just in case, because i didn't know any better:
Code:
rm -fr .accounts/*
rm -fr .activesync/*
rm -fr .aegis/*
Still now i get crashes after installing an app using dpkg or apt-get. I mean, terminal window and open apps closing after final phase of an install process - 'updating desktop entries'. So i have to run some n9qtweaks multiple times to get everything installed.

Can somebody hint what could be wrong. Or what are the correct flashing commands, after disabling the warning message.

Last edited by veeall; 2020-07-22 at 16:24.
 

The Following User Says Thank You to veeall For This Useful Post: