With the permission of the creator of the firmware
Version 03/05/2016 - based on V7.1.3.0.LHPCNCKand at the request of users briefly describe
flashing process firmware (that is, semi-Russian semi-English firmware from sellers under the number MIUI 77.2.1)
to our modified Russian firmware (as in this description or any other as a system.img file)
on linux ubuntu .
I myself am a teapot in mid-level Linux, I do not pretend to the depth of knowledge, I did it as I could find crumbs on the net, which I spent about 5 hours of time and nerve cells in a couple of moments)0
All commands are executed in the Linux computer, not in the phone (unless otherwise specified)! The phone is in the "connect-disconnect" role.1. How to connect Xiaomi Redmi 3 via adb. 1.1 We set up checkboxes and update server as on screenshots
1.2 We install adb (and fastboot just in case) through the terminal:
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
1.3 We are trying to connect the device (turned on, with the "USB debugging" checkbox checked) with the command
adb devices . I gave an empty list, the device was not found myself. Are looking for. We kill "bad while" adb team
adb kill-server .
1.4 Team
lsusb without a connected phone, display a list of all usb currently connected to the computer. We memorize it slightly. Connect tel. Again
lsusb . We see that 1 device has become more (and it is without a name, unlike the others). We remember his ID, that before the colon (I had 2717: ff48).
1.5 Create an empty file in the home folder in the .android subfolder named adb_usb.ini. We write there 0x2717 and save.
1.6 Create in /etc/udev/rules.d/ file 51-android.rules (or edit the existing one) with the addition to the end of the line (separated by commas) or a single line:
SUBSYSTEM == "usb", ATTR {idVendor} == "2717, MODE =" 0666 #Xiaomi Redmi 3
1.7 Checking
adb devices , the device should appear! While offline, there will be a window on the phone confirming the USB debugging connection, click YES, again
adb devices and cheers, online status, the device is there. You can "do anything with it")
2. How to flash Xiaomi Redmi 3 with the system.img file via adb. 2.0 Ruth should be (in the apk header).
2.1 Flash the Vietnamese system.img file by manual
from heredoes not work, writes that "Operation permitted", so a different way.
2.2 Build.prop
phone (directly from the phone via any root explorer along the path /system/build.prop) we change the very version from MIUI77.1.2 to MIUI7.1.2 (delete the extra seven!) in the line ro.build.version.incremental = .. .
2.3 The phone immediately starts looking for an update over the air, downloads it, such as MIUI 7.1.3 stable or something new (or we are looking for it manually in the System Updates), install it. 716MB Everything seems fine, but English ..
(I would have left this version myself, but I did everything for my wife, she needs Russian)2.4 Quickly skip all the initial settings of the phone, set the root again, reboot the bodies (necessarily! Otherwise adb will not be included in su)
2.5 Copy system.img (2.4Gb) to the root of the memory card or the root of the internal memory of the phone, where you prefer.
2.5 Tel is ready, turned on, we connect
adb devices do it in turn:
adb shell
su
dd if = / storage / sdcard1 / system.img of = / dev / block / mmcblk0p23
Or change the path to
/data/media/0/system.imgif the file is in the phone.
2.6 Type command will hang. The process has begun! ) At the end can issue
root @ ido: / # dd if = / data / media / 0 / system.img bs = 4096 of = / dev / block / mmcblk0p23
Illegal instruction
132 | root @ ido: / #
This is as experience shows, not scary. System.img was completely sewn, not drift
(from the phone's memory will give the same error, checked).
2.7 The phone is included in an interesting view - the desktop is there, but not a single application starts. So it is necessary)
2.8 Reboot.
2.9 Starting a new flash with an elephant (or another logo), two minutes.
2.10 Load, skip all settings again, enable debugging, do
Again, will give out that something could not be removed, not scary. Reboot tel.
2.11 This start will be just before that, about 15 minutes. If it’s more than that, by long pressing the power button, we force the body to overload.
2.12 Minutes after 3 bodies will load, skip all the settings, do a full reset to factory settings. (Maybe not necessarily, but I did).
Post has been editedCamerado - 28.08.16, 12:48