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!!
Hello,
I need help to unbrick my phone please,
After trying to back to stock i got stuck while dload method with BLL-L22C636B150 (android 6.0) Firmware after flashing RollbackPackage from same firmware (android 7.0 to 6.0)
My phone's screen is now only black, no boot logo anymore or recovery.
It's only show connected fastboot while plug in, i can only reboot to fastboot.
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.006s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.005s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7XXXX
(bootloader) IMEI:8646XXXX
(bootloader) IMEI1:8646XXXX
What can i do please ?
Try team mt tool for unbrick provide file from marshmallow update.app
siddhrsh said:
Try team mt tool for unbrick provide file from marshmallow update.app
Click to expand...
Click to collapse
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Demodark said:
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Click to expand...
Click to collapse
Did you flash marshmallow files
Images
Yes i tried to unbrick with : Huawei_GR5_2017_BLL-22_C636B150_South_East_Asia_6.0.zip
17:49:30: All images are found, everything is ready for the unbricking process.
17:49:32: Unbricking started. Your computer may freezes during the process.
17:49:32: flash boot "C:\adb\B150\boot.img"
17:49:34: The Boot image is flashing successfully
17:49:34: flash system "C:\adb\B150\system.img"
17:52:03: The System image is flashing successfully
17:52:03: flash cust "C:\adb\B150\cust.img"
17:52:26: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 12.833s]
writing 'cust' 1/2...
OKAY [ 3.181s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.114s]
writing 'cust' 2/2...
OKAY [ 0.045s]
finished. total time: 16.173s
17:52:26: Error#1
17:52:26: flash recovery "C:\adb\B150\recovery.img"
17:52:29: The Recovery image is flashing successfully
17:52:29: flash userdata "C:\adb\B150\userdata.img"
17:52:36: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.784s]
writing 'userdata'...
OKAY [ 1.013s]
finished. total time: 4.797s
17:52:36: Error#1
17:52:36: Completed
17:52:36: Something went wrong (((
Huawei Multi-Tool by Team MT v. 8.0.3.1 beta
I dont know wich one i can try now ?
http://pro-teammt.ru/firmware-database/?firmware_model=bll-l22&firmware_page=0
Black Screen
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Demodark said:
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Click to expand...
Click to collapse
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
shashank1320 said:
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
Click to expand...
Click to collapse
What is "the small data file" please ?
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.007s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.006s]
finished. total time: 0.006s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.006s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7N17609000963
(bootloader) IMEI:864646034450028
(bootloader) IMEI1:864646034717855
OKAY [ 0.005s]
finished. total time: 0.005s
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
PS C:\adb>
Demodark said:
What is "the small data file" please ?
Click to expand...
Click to collapse
Let me check the firmware and get the link for you
shashank1320 said:
Let me check the firmware and get the link for you
Click to expand...
Click to collapse
News ?
Demodark said:
News ?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
shashank1320 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
Click to expand...
Click to collapse
Link is dead.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
Let me recheck
What can i do ?
Always black screen, but phone detected as fastboot mode, reboot only leads to fastboot mode.
have you tried unlocking again your bootloader? updating or rollbacking of EMUI makes your bootloader locked by default.
try to unlock it first and flash your OS
if you want to use the dload way. try flashing the stock recovery after unlocking your bootloader.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
K.. But after that how reset the DNS to its original state
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.
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
SAMPPLE said:
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Homeboy76 said:
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Click to expand...
Click to collapse
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
SAMPPLE said:
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
Click to expand...
Click to collapse
What did you try to exit fastboot?
Homeboy76 said:
What did you try to exit fastboot?
Click to expand...
Click to collapse
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
SAMPPLE said:
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
Click to expand...
Click to collapse
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Homeboy76 said:
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Click to expand...
Click to collapse
I know I tried a lot of things to make it work... but nothing... Anyway thank you for helping me
put it in the freezer for an hour and tell me what happens, mine booted up with that, just put it in properly (all phone holes covered)