Help Needed Please. Please Read - Google Pixel Questions & Answers

Before I start, I really hope some one can help. I'm pretty good with computer stuff just not an expert. I have a Pixel XL from Verizon with an unlocked boot loader, using minimal and adb tool that is currently recognizing my device in fast-boot. i either want to get to a point where i can root and install a custom ROM or just return to a stock image for now. I hate being without a phone. I miss my nexus 6P and the NRT from wugfresh so simple and easy. Okay so here's what happened.
1. I unlocked my boot loader.
2. I was trying to root with skipsoft ( i know there's an easier way to root now) and got all the way to where I had to fine the ZIP TWRP file to flash it on the device but could not find it on the actual device no matter where I looked even in the folder the program told me where it was being copied too.
3. So I restarted my pixel XL and restarted the Skipsoft tool kit and then just boot loops.
4. I tried to "Flash-all.bat" on a factory image from google with no success. I keep getting these messages:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.845s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.024s]
finished. total time: 2.869s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.063s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.497s]
writing 'radio_a'...
OKAY [ 0.464s]
finished. total time: 1.962s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (29 MB) to disk... took 1.039s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1761 MB) to disk...W/ziparchive( 6032): Zip: unable to truncate file to 1846804736: File too large
error:
failed to extract 'system.img': I/O error
Any help would be greatly appreciated.

Thread moved to Q&A

@Chabot1987 how much free space do u have on your HDD?

Yep, check your computer's hard drive space, and check the sha-256 of the image zip.

Update, Some how i was able to flash TWRP and then install a custom rom. alot of fiddling around with stuff but i think i have it lol, thank you for the response though, also i barley had any actually i have a HP stream so barley anything on it. could that of been the problem?

Chabot1987 said:
Before I start, I really hope some one can help. I'm pretty good with computer stuff just not an expert. I have a Pixel XL from Verizon with an unlocked boot loader, using minimal and adb tool that is currently recognizing my device in fast-boot. i either want to get to a point where i can root and install a custom ROM or just return to a stock image for now. I hate being without a phone. I miss my nexus 6P and the NRT from wugfresh so simple and easy. Okay so here's what happened.
1. I unlocked my boot loader.
2. I was trying to root with skipsoft ( i know there's an easier way to root now) and got all the way to where I had to fine the ZIP TWRP file to flash it on the device but could not find it on the actual device no matter where I looked even in the folder the program told me where it was being copied too.
3. So I restarted my pixel XL and restarted the Skipsoft tool kit and then just boot loops.
4. I tried to "Flash-all.bat" on a factory image from google with no success. I keep getting these messages:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.845s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.024s]
finished. total time: 2.869s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.063s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.497s]
writing 'radio_a'...
OKAY [ 0.464s]
finished. total time: 1.962s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (29 MB) to disk... took 1.039s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1761 MB) to disk...W/ziparchive( 6032): Zip: unable to truncate file to 1846804736: File too large
error:
failed to extract 'system.img': I/O error
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I get the same error message as above. How did you get back to stock? Per other replies, I checked free space and sha-256 of the image zip, and both OK.

Related

[Q] 5.0 OTA Fails

I made sure everything is up to date. I'm trying to flash the 5.0 OTA, but it keeps failing and I don't know why. I went into platform tools and pasted the extracted lollipop download, held shift and right clicked, opened up the command prompt and did the following. I made sure USB debugging was enabled. I've also tried it by using the command adb reboot bootloader from the homescreen to get into fastboot. It doesn't matter what I do, it always fails the same way. I have never had this issue. What the hell is going on?
C:\Users\Raistlin\ADT\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb
devices
List of devices attached
C:\Users\Raistlin\ADT\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>flas
h-all
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.295s]
writing 'bootloader'...
OKAY [ 0.481s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.121s
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.662s]
writing 'radio'...
OKAY [ 3.127s]
finished. total time: 4.793s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.111s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1005154516 bytes
error: update package missing system.img
Press any key to exit...

Never seen a brick this hard to solve...

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!!

[GUIDE][ROM][STOCK] XT1766 Stock Firmware & Restoration Guide

Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.
Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?
error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.
UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide​
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>

[Guide] How to flash stock ROM on Redmi Go

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.

Can not flash factory img:

Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Code:
C:\Users\XXXX>fastboot flash bootloader "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\bootloader-sargo-b4s4-0.2-5736883.img"
target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.586s]
finished. total time: 0.865s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\XXX>fastboot flash radio "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\radio-sargo-g670-00025-190805-b-5781381.img"
target reported max download size of 268435456 bytes
sending 'radio' (73196 KB)...
OKAY [ 1.673s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_b
OKAY [ 0.555s]
finished. total time: 2.244s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.053s
C:\Users\XXX>fastboot -w update "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\image-sargo-qp1a.191105.003.zip"
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ (15016): Zip: unable to truncate file to 485105848: File too large
failed to extract 'vendor.img': I/O Error
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 97AAY1041S
--------------------------------------------
checking product...
OKAY [ 0.053s]
checking version-bootloader...
OKAY [ 0.063s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (65536 KB)...
OKAY [ 1.520s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.006s
Thank you in advance!
Simon
simhagen said:
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Thank you in advance!
Simon
Click to expand...
Click to collapse
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Horgar said:
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Click to expand...
Click to collapse
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Code:
[[email protected] MyApplication]$ sudo fastboot flash bootloader /home/XXXX/Downloads/sargo-pd2a.190115.029/bootloader-sargo-b4s4-0.1-5262905.img
Sending 'bootloader_b' (8349 KB) OKAY [ 0.340s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.1-5262905
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.541s]
Finished. Total time: 1.074s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot flash radio /home/XXXX/Downloads/sargo-pd2a.190115.029/radio-sargo-g670-00011-190213-b-5306579.img
Sending 'radio_b' (72988 KB) OKAY [ 2.230s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00011-190213-B-5306579
(bootloader) Flashing partition modem_b
OKAY [ 0.880s]
Finished. Total time: 3.315s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot update -w /home/XXXX/Downloads/sargo-pd2a.190115.029/image-sargo-pd2a.190115.029.zip
--------------------------------------------
Bootloader Version...: b4s4-0.1-5262905
Baseband Version.....: g670-00011-190213-B-5306579
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.051s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' OKAY [ 0.063s]
extracting boot.img (64 MB) to disk... took 0.284s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.990s]
Writing 'boot_b' OKAY [ 0.729s]
extracting dtbo.img (8 MB) to disk... took 0.056s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.340s]
Writing 'dtbo_b' OKAY [ 0.133s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.064s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2271 MB) to disk... took 11.015s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 7.389s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 7.840s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 7.830s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 7.760s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 7.870s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 8/9 (258620 KB) OKAY [ 7.690s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 9/9 (232288 KB) OKAY [ 7.020s]
Writing 'system_b' OKAY [ 1.920s]
archive does not contain 'system_ext.img'
extracting system_other.img (391 MB) to disk... took 1.914s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/2 (262140 KB) OKAY [ 7.850s]
Writing 'system_a' OKAY [ 0.370s]
Sending sparse 'system_a' 2/2 (138668 KB) OKAY [ 4.200s]
Writing 'system_a' OKAY [ 1.380s]
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
sic0048 said:
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Click to expand...
Click to collapse
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Horgar said:
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Click to expand...
Click to collapse
Thanks,
link does not work for me though...
simhagen said:
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
Click to expand...
Click to collapse
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
For example, if you have ADB installed on your C: drive and your C: drive doesn't have several GB of storage space available, you will get this error. It won't help if you have space available on other drives, because ADB only interacts with the folder it is installed on. So having 100 GB free on another drive won't help as an example.
sic0048 said:
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
Click to expand...
Click to collapse
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
simhagen said:
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
Click to expand...
Click to collapse
No. As long as that space is available on your main drive (see my edit above), 30 GB should be plenty of space. I'm thinking it takes around 5 GB if I remember correctly.
simhagen said:
Thanks,
link does not work for me though...
Click to expand...
Click to collapse
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Try this
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
Code:
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
under Windows I didn't get this problem. So system is up and running again.
Thank you!
simhagen said:
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
under Windows I didn't get this problem. So system is up and running again.
Thank you!
Click to expand...
Click to collapse
Glad to hear you're sorted. It took me a while to work out I just needed to update fastboot. Someone on XDA helped me with it.
simhagen said:
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Click to expand...
Click to collapse
I had the exact same problem as you did. I tried different versions of the stock ROM, I tried different versions of the fastboot tool (including sdkmanager --update to get to the latest, etc.). It failed at the same time, every time: "Sending sparse 'vendor_a'"
What actually worked for me was plugging the USB cable into a port directly on the laptop, instead of a hub built into the docking station.
**** you not, worked perfectly. Same cable, same fastboot binary, same laptop, same OS, just switching to a different port did the trick. Don't plug the cable into a USB hub.

Categories

Resources