So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!
My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?
Ahlangwolf said:
My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?
Click to expand...
Click to collapse
The bootloader is not unlocked, you must block with fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader
jftorrente said:
The bootloader is not unlocked, you must block with fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader
Click to expand...
Click to collapse
And make sure to go to Developer options when booted and enable OEM unlock.
Both Phone and FRP must be unlocked in fastboot
ante0 said:
And make sure to go to Developer options when booted and enable OEM unlock.
Both Phone and FRP must be unlocked in fastboot
Click to expand...
Click to collapse
The same happened to me, I checked and it appeared unlocked but it did not let me install the recovery. so I relocked it and unlocked it and that's how it worked
jftorrente said:
The same happened to me, I checked and it appeared unlocked but it did not let me install the recovery. so I relocked it and unlocked it and that's how it worked
Click to expand...
Click to collapse
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.
Ahlangwolf said:
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.
Click to expand...
Click to collapse
:good::good::good::good:
Great, now read the Forum Rules on posting, moved out of the Development Section....
Ahlangwolf said:
My phone is unlocked already. but I still could not flash TWRP into partition. Any one can help?
Code:
fastboot flash recovery_ramdisk twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (65536 KB)...
OKAY [ 1.402s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.421s
Code:
D:\>fastboot flash recovery twrp_3.1.1_recovery_orig.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.407s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.424s
Anyone met that?
Click to expand...
Click to collapse
Ahlangwolf said:
Thank you for the mention. I relocked and unlocked again on B332 version get resolved.
Click to expand...
Click to collapse
do i have to execute this? fastboot oem relock XXXXXXXXXXX and re-unlock the bootloader , what is the xxxxxxxx? TIA
you must be disable find phone and fingepin
If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM.
Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error.
But, there is a way!
Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time)
CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device.
Requirements
- Unlocked Bootloader
- Xiaomi USB drivers installed on your PC
- PC/TWRP
- microSD Card
- Minimal ADB & Fastboot (If using PC)
- V10.2.6.0.OCLMIXM ROM zip file (Download here
-V10.2.7.0.OCLMIXM (Download here
At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later).
Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card.
Steps, if you're using PC
1. Install Minimal ADB & Fastboot (Download here)
2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed.
3. Run "cmd-here" and type fastboot flash recovery recovery.img
4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together.
5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Steps, if you're using TWRP
1. Copy the "recovery.img" file that you extracted earlier, to your SD Card.
2. Boot TWRP
3. Select Install
4. Select Install Image
5. Locate the "recovery.img" file in your SD Card and install it.
6. Go back to main menu and reboot into recovery.
7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Your device should now be running clean stock ROM and recovery.
Don't forget to hit Thanks Button if you found this useful.
As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot.
The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one.
Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried).
Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html
This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ):
Boot Image Patching
This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead.
In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image.
Copy the boot image to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot image file
Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices:
fastboot flash boot /path/to/magisk_patched.img
-----------------
Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html
Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA).
https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/
And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction.
I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever.
Actually tried an easier way:
Just download the tgz file from mi website tiare_global_images_V10.2.6.0.OCLMIXM_20190218.0000.00_8.1_66cc42a821.tgz
If you are on linux it is easy tar xvf filename
Code:
tiare_global_images_V10.2.6.0.OCLMIXM_8.1$ ls -R
.:
flash_all.bat flash_all_except_data_storage.sh flash_all_lock.sh flash_gen_crc_list.py flash_gen_resparsecount md5sum.xml
flash_all_except_data_storage.bat flash_all_lock.bat flash_all.sh flash_gen_md5_list.py images misc.txt
./images:
adspso.bin crclist.txt gpt_both0.bin NON-HLOS.bin prog_emmc_firehose_8917_lite.mbn sbl1.mbn userdata.img
boot.img devcfg.mbn gpt_main0.bin partition.xml rawprogram0_BLANK.xml sparsecrclist.txt vendor.img
cache.img elf_path.txt keymaster64.mbn patch0.xml rawprogram0.xml splash.img
cmnlib_30.mbn emmc_appsboot.mbn keymaster.mbn persist.img recovery.img system.img
cmnlib64_30.mbn gpt_backup0.bin lksecapp.mbn prog_emmc_firehose_8917_ddr.mbn rpm.mbn tz.mbn
$ chmod +x flash_all_lock.sh
$ ./flash_all_lock.sh
tiare Fastboot Tool Ver 3.0
product: tiare
target reported max download size of 535822336 bytes
sending 'partition' (33 KB)...
OKAY [ 0.004s]
writing 'partition'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.010s
target reported max download size of 535822336 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.002s]
writing 'crclist'...
OKAY [ 0.006s]
finished. total time: 0.009s
target reported max download size of 535822336 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.002s]
writing 'sparsecrclist'...
OKAY [ 0.006s]
finished. total time: 0.008s
target reported max download size of 535822336 bytes
sending 'tz' (1503 KB)...
OKAY [ 0.055s]
writing 'tz'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.062s
target reported max download size of 535822336 bytes
sending 'sbl1' (342 KB)...
OKAY [ 0.014s]
writing 'sbl1'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.020s
target reported max download size of 535822336 bytes
sending 'rpm' (180 KB)...
OKAY [ 0.009s]
writing 'rpm'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.015s
target reported max download size of 535822336 bytes
sending 'aboot' (559 KB)...
OKAY [ 0.024s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.030s
target reported max download size of 535822336 bytes
sending 'tzbak' (1503 KB)...
OKAY [ 0.056s]
writing 'tzbak'...
OKAY [ 0.064s]
finished. total time: 0.120s
target reported max download size of 535822336 bytes
sending 'sbl1bak' (342 KB)...
OKAY [ 0.015s]
writing 'sbl1bak'...
OKAY [ 0.024s]
finished. total time: 0.040s
target reported max download size of 535822336 bytes
sending 'rpmbak' (180 KB)...
OKAY [ 0.009s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.030s
target reported max download size of 535822336 bytes
sending 'abootbak' (559 KB)...
OKAY [ 0.023s]
writing 'abootbak'...
OKAY [ 0.034s]
finished. total time: 0.057s
target reported max download size of 535822336 bytes
sending 'devcfg' (60 KB)...
OKAY [ 0.004s]
writing 'devcfg'...
OKAY [ 0.014s]
finished. total time: 0.018s
target reported max download size of 535822336 bytes
sending 'cmnlib' (208 KB)...
OKAY [ 0.010s]
writing 'cmnlib'...
OKAY [ 0.022s]
finished. total time: 0.032s
target reported max download size of 535822336 bytes
sending 'cmnlib64' (262 KB)...
OKAY [ 0.012s]
writing 'cmnlib64'...
OKAY [ 0.023s]
finished. total time: 0.035s
target reported max download size of 535822336 bytes
sending 'keymaster' (265 KB)...
OKAY [ 0.012s]
writing 'keymaster'...
OKAY [ 0.023s]
finished. total time: 0.035s
target reported max download size of 535822336 bytes
sending 'devcfgbak' (60 KB)...
OKAY [ 0.004s]
writing 'devcfgbak'...
OKAY [ 0.014s]
finished. total time: 0.018s
target reported max download size of 535822336 bytes
sending 'cmnlibbak' (208 KB)...
OKAY [ 0.010s]
writing 'cmnlibbak'...
OKAY [ 0.023s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'cmnlib64bak' (262 KB)...
OKAY [ 0.013s]
writing 'cmnlib64bak'...
OKAY [ 0.023s]
finished. total time: 0.036s
target reported max download size of 535822336 bytes
sending 'keymasterbak' (265 KB)...
OKAY [ 0.012s]
writing 'keymasterbak'...
OKAY [ 0.025s]
finished. total time: 0.038s
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.584s]
writing 'dsp'...
OKAY [ 0.550s]
finished. total time: 1.134s
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'apdp'...
OKAY [ 0.013s]
finished. total time: 0.013s
erasing 'msadp'...
OKAY [ 0.013s]
finished. total time: 0.013s
target reported max download size of 535822336 bytes
sending 'modem' (86016 KB)...
OKAY [ 3.050s]
writing 'modem'...
OKAY [ 3.022s]
finished. total time: 6.072s
target reported max download size of 535822336 bytes
erasing 'system'...
OKAY [ 0.160s]
sending sparse 'system' (502636 KB)...
OKAY [ 19.755s]
writing 'system'...
OKAY [ 17.618s]
sending sparse 'system' (523260 KB)...
OKAY [ 20.561s]
writing 'system'...
OKAY [ 18.747s]
sending sparse 'system' (115276 KB)...
OKAY [ 4.530s]
writing 'system'...
OKAY [ 4.084s]
finished. total time: 85.454s
target reported max download size of 535822336 bytes
erasing 'cache'...
OKAY [ 0.011s]
sending 'cache' (140 KB)...
OKAY [ 0.008s]
writing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'userdata' (192 KB)...
OKAY [ 0.009s]
writing 'userdata'...
OKAY [ 0.023s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'recovery' (20207 KB)...
OKAY [ 0.717s]
writing 'recovery'...
OKAY [ 0.670s]
finished. total time: 1.387s
target reported max download size of 535822336 bytes
sending 'boot' (15547 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.581s]
finished. total time: 1.135s
target reported max download size of 535822336 bytes
sending 'splash' (10802 KB)...
OKAY [ 0.380s]
writing 'splash'...
OKAY [ 0.366s]
finished. total time: 0.747s
target reported max download size of 535822336 bytes
sending 'vendor' (278000 KB)...
OKAY [ 9.794s]
writing 'vendor'...
OKAY [ 9.957s]
finished. total time: 19.751s
...
OKAY [ 0.057s]
finished. total time: 0.057s
rebooting...
finished. total time: 0.061s
System fresh as NEW.
Note that there is a newer version: 10.2.12
Sadly the phone even AOSP with just whatsapp and email becomes very slow. Flashed stock return to retailer!
hello.
weareinwarwithbugs said:
As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot.
The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one.
Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried).
Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html
This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ):
Boot Image Patching
This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead.
In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image.
Copy the boot image to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot image file
Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices:
fastboot flash boot /path/to/magisk_patched.img
-----------------
Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html
Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA).
https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/
And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction.
I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever.
Click to expand...
Click to collapse
Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry
a rdz said:
Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry
Click to expand...
Click to collapse
I didn't use twrp at all.
I used Miflash instead of twrp as I told above, in order to restore previous state of the device.
If you did update, as one of the ways I see then, is to replace it with stock rom from which you are going to take the boot image from, to patch with magisk. Do no update. Root first. I have not updated so I don't know how the updating after rooting is going to work. No twrp needed if you just want root.
---------- Post added at 10:58 AM ---------- Previous post was at 10:07 AM ----------
There's slightly different address now: http://c.mi.com/oc/miuidownload/index. Going mi.com or https://en.miui.com/ and clicking downloads if doesn't get there.
RafiAhmed said:
If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM.
Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error.
But, there is a way!
Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time)
CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device.
Requirements
- Unlocked Bootloader
- Xiaomi USB drivers installed on your PC
- PC/TWRP
- microSD Card
- Minimal ADB & Fastboot (If using PC)
- V10.2.6.0.OCLMIXM ROM zip file (Download here
-V10.2.7.0.OCLMIXM (Download here
At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later).
Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card.
Steps, if you're using PC
1. Install Minimal ADB & Fastboot (Download here)
2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed.
3. Run "cmd-here" and type fastboot flash recovery recovery.img
4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together.
5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Steps, if you're using TWRP
1. Copy the "recovery.img" file that you extracted earlier, to your SD Card.
2. Boot TWRP
3. Select Install
4. Select Install Image
5. Locate the "recovery.img" file in your SD Card and install it.
6. Go back to main menu and reboot into recovery.
7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Your device should now be running clean stock ROM and recovery.
Don't forget to hit Thanks Button if you found this useful.
Click to expand...
Click to collapse
Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update?
edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader.
Request for miui custom ROM for Redmi go
Can anyone built new miui custom ROM port for e
Redmi go:good:
Like it, thank you
matador84 said:
Note that there is a newer version: 10.2.12 ?
V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/
Click to expand...
Click to collapse
fmcgorenc said:
Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update?
edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader.
Click to expand...
Click to collapse
Glad to know that it helped you. And yes, you can update every time after restoring by using this method. It actually takes you to 100% stock condition.
JonnyTech said:
matador84 said:
Note that there is a newer version: 10.2.12 ?
V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/
Click to expand...
Click to collapse
The one I mentioned is targeted to take the phone back to the state it was in, after you purchased it.
Click to expand...
Click to collapse
Failed to installing
while applying update from sd card it's failing to install. Anything can i do?
plz help if there is any idea
How out of date this guide really is?
dustojnikhummer said:
How out of date this guide really is?
Click to expand...
Click to collapse
It still works.
Hakhim said:
while applying update from sd card it's failing to install. Anything can i do?
plz help if there is any idea
Click to expand...
Click to collapse
I'm sorry, I might've been busy or didn't notice when you posted this. Did you manage to fix it?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP
Sid160706 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP
Click to expand...
Click to collapse
this worked perfectly. i cleared system, dalvik, cache, data in twrp, then flashed latest V10.2.25.0.OCLMIXM, phone rebooted and showed encryption unsuccessful, i clicked on erase everything then it encryted and booted successfully.
Hi guys!
I don't seem to be able to flash TWRP 3.3.1 onto my pie phone. From Linux, I get the following:
Code:
:$ fastboot flash recovery ./recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 3.554s]
writing 'recovery'...
OKAY [ 0.942s]
finished. total time: 4.496s
The phone doesn't even blink. If I manually reboot it, nothing has happened. If I get to the recovery menu, I get the MI-Recovery 3.0.
What am I doing wrong? How should I be doing it?
Thanks!
To reboot to recovery : vol+ and power twice
I am stuck with the same problem. Is there any way to resize recovery partition? Or could someone send me stock recovery? Thx
EDIT: I managed to fix. Russian TWRP from 4PDA works.
timonoj said:
Hi guys!
I don't seem to be able to flash TWRP 3.3.1 onto my pie phone. From Linux, I get the following:
Code:
:$ fastboot flash recovery ./recovery-TWRP-3.3.1-0602-REDMI6-CN-wzsx150.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 3.554s]
writing 'recovery'...
OKAY [ 0.942s]
finished. total time: 4.496s
The phone doesn't even blink. If I manually reboot it, nothing has happened. If I get to the recovery menu, I get the MI-Recovery 3.0.
What am I doing wrong? How should I be doing it?
Thanks!
Click to expand...
Click to collapse
Kindly ensure that you are using the correct device image. If you flash the wrong image/other device image then it will always boot in mi recovery 3.0.
Here is the link : Xiaomi Redmi 6 (twrp.me)