i'm not sure
I try now to flash a new firmware from the Github (it's ok), but if I flash my firmware again, it will be locked. So it seems that the "migrate" from 5.5.6 firmware to the new firmware is problematic
A:
The problem is the the device is not responding with a response code of "OK" and "100".
Instead it returns the response code "ERROR" and "100".
That means the device is not in recovery mode.
The device is booting to the stock firmware when the migration fails.
When the migration fails the device is booting to the stock firmware, the migration will return error "100" to the host, but this device is not responding with the "OK" and "100" response code.
To resolve the issue we must reset the device to the factory default configuration before we upgrade.
We can do that by connecting the device to a windows computer, just restart the device.
Then we need to write the bootloader to the micro-SD card, which can be done by running the following command.
fastboot oem write_flash
Now we can flash the new firmware.
Here is a tutorial on how to write a stock firmware and recover it by Odin.
You can also download Odin 3.12 and use it to flash the new firmware.
Source
Q:
Django, foreign keys and models.py
I have three models:
class Page(models.Model):
title = models.CharField(max_length=30)
class Article(models.Model):
author = models.ForeignKey(Person, on_delete=models.CASCADE)
title = models.CharField(max_length=40)
class Comment(models.Model):
article = models.ForeignKey(Article, on_delete=models.CASCADE)
comment_text = models.TextField()
The problem is that whenever I create the Article model, it already exists, because all the other models are in models.py file in the same directory. How can I overcome that?
Firstly you need to run manage.py syncdb to create the database tables. Then you can run the app directly with python manage.py runserver.
Related links: