Red Rice 1 s W/C version feasible dual system solution (only analysis has not been implemented), Red Rice 1 s

Red Rice 1 s W/C version feasible dual system solution (only analysis has not been implemented), Red Rice 1 s

Benefit from the bl source code of the redmi 1 s telecom/Unicom version, which is cracked by balika011 and released by the foreign god (I have already fork it on git, address: https://github.com/syhost/lk-armani, and can be used normally ), this model can be compiled by a third party and can be started on dual systems.

Combined with the dual-system of Xiaomi 2 and the dual-system solution of pantai A820L, refer to my previous dual-system solution:

Http://bbs.anzhi.com/thread-5931961-1-1.html

Analyze the dual-system solutions available for the China Telecom/China Unicom version of redmi 1 s:

1. Similar to Xiaomi 2, emmc (internal storage) needs to be re-partitioned and new partitions such as system1 and boot1 need to be supported by bl and recovery. The disadvantage of this solution is that re-partitioning is required, poor operability. The advantage is that there is a reference for Xiaomi 2. You do not need to perform special processing on the recovery and bl support, and the solution is also relatively mature.

2. Similar to my previous pan-Thai A820L, the second system is flushed to an external TF card. The advantage of this solution is that you do not need to re-partition the internal storage. You only need support for bl and refresh, the disadvantage is that you need to modify the fl, re-partition the external card, and require a high speed for the external TF card. In addition, the specific operation of this solution can be divided into several methods:

1) data partitions and other partitions are all on the external card, so that the two systems are completely unrelated. The disadvantage is that the external card is slow and may affect system performance.

2) data partitions are shared with systems on the internal storage. This is actually similar to the dual system of Xiaomi 2, because the system and other partitions except data partitions do not need to be read and written at any time, therefore, the system performance should be slightly different from the internal storage. The disadvantage is that the two systems may interfere with data.

3) the above two methods need to be modified, and an external card partition package (Card swipe) should be made separately. In addition, recovery and bl can be processed, in this way, you can choose to fl an external card or a built-in card (similar to the recovery of Xiaomi 2) When you fl the machine, and use bl to determine where to start the system, this method is more operable, but there is no clear idea about the specific implementation method (the above solutions are successful cases ..)

3. In addition to the above solution, refer to other people's dual-system implementation, you can also modify init or boot to implement it. There are specific operational methods, which will not be described in detail here!