Develop Bugs

[HELP] Help with fastboot and RSD Lite

The phone doesn't show up in RSD Lite
But in my ADB ( $- Fastboot devices) it's showing up.
Can someone help me?
Downloaded and installed:
Device Manager
Moto USB Drivers
Moto Service (doesn't appear here too)
My brother give me this phone, and doesn't know the Gmail account he use (yeah i'm furious, he created a account just to "test" the phone, now i'm stuck in the google login screen because he wipes the phone in bootloader)
Windows 10
Motorola USB Cable
Print:
http://prntscr.com/gcrqab

What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required

TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
I can do it with bootloader locked?
i"m with FRP (Factory Reset Protection) i can't pass without the gmail that he created and doesn't even remember the email.

TeuzHd said:
I can do it with bootloader locked?
Click to expand...
Click to collapse
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms

TheFixItMan said:
What are you attempting to do?
If you are trying to flash firmware you do it through fastboot
If you are trying to log into google just create and sign in with a different account
Commands to flash via fastboot once you have downloaded the firmware are
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Note if you have more sparsechunks flash them as well in number order
If you want to play it safe and only really flash what should get the phone booting again just flash
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
Again if you have more sparsechunks flash them as well in number order
I don't know what that tool you are using is but it's not required
Click to expand...
Click to collapse
TheFixItMan said:
Yes if it's original Motorola firmware
You only need to unlock bootloader for custom firmware/roms
Click to expand...
Click to collapse
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld

TeuzHd said:
I'm getting this with everything:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
That's my ADB root folder: http://prntscr.com/gcz5ld
Click to expand...
Click to collapse
from that you should be typing the following
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
The errors you are getting is because of your adb version - it should still flash
long as you get an output that looks like this at the end
Code:
sending 'logo' (460 KB)...
OKAY [ 0.099s]
writing 'logo'...
OKAY [ 0.154s]
finished. total time: 0.256s
I have encluded my adb and fastboot folder for you to use (excludes any firmware just adb and fastboot) for use on windows
Download from link below
Platform-tools

TheFixItMan said:
from that you should be typing the following
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse

TeuzHd said:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.722s[/HTML]
i can try with another PC, should work?
Click to expand...
Click to collapse
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash

TheFixItMan said:
The firmware you are trying to flash is a lower version than what is installed - You must get firmware that is equal to or newer than the firmware on the device already else it will fail
eg you cant flash android 7.0 on a device that has a bootloader that is for 7.1
you will have to find the correct firmware for your device
note there is no harm trying the firmware because as you can see - if its wrong it will just fail the validation test and not flash
Click to expand...
Click to collapse
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device

try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
TeuzHd said:
Reflashing the 7.1.2 version i can pass FRP? i'm trying to bypas FRP.
In the authorized warranty, they told me that they can not do any software repairs on the device until I remove the FRP, but as I said we do not know the account he used to "test" the device
Click to expand...
Click to collapse
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device

TheFixItMan said:
try adding this to the list of fastboot commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
---------- Post added at 06:24 PM ---------- Previous post was at 06:21 PM ----------
best thing is to google
eg
https://www.progeeksblog.com/frp-bypass-apk/
Iv never had do anything with frp so no idea how to do it on this device
Click to expand...
Click to collapse
I did this, but the APK and Share exploit's doesn't work anymore

do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore

TheFixItMan said:
do you mean there is a password on the device because you can bypass that easy
just goto twrp
advanced
file manager
data
system
click on each of the following files and delete
gatekeeper-password.key
gatekeeper-patten.key
locksettings.db-shm
locksettings.db-wal
other than that I can't help anymore
Click to expand...
Click to collapse
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP

TeuzHd said:
can't start TWRP
1- bootload locked with ADB options OFF
to put adb options on i need to pass FRP
Click to expand...
Click to collapse
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial

TheFixItMan said:
have you tried
https://www.youtube.com/watch?v=xhf9egv8-ys
uses this app
https://play.google.com/store/apps/details?id=com.wUnlockiOfficial
Click to expand...
Click to collapse
How can i install a app without pass FRP?

TeuzHd said:
How can i install a app without pass FRP?
Click to expand...
Click to collapse
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you

TheFixItMan said:
Do some googling
https://youtu.be/GkmL5tUtyB0
With this tool
http://www.mediafire.com/file/yif2m8j11dx1ur8/Moto+G4+Plus+Google+Account.rar
Watch videos and Google - don't rely on me to search for thing for you
Click to expand...
Click to collapse
i alredy do this, look in the thread

Hi,
Where I can download the last firmware for Moto G5 XT1676 ?

problem with my z2 force

I have this Z2 Force, but it has this problem, since it does not pass this screen, I connect it to my computer and it does not detect it, it has a solution or someone that can help me solve this problem.

martin13x said:
I have this Z2 Force, but it has this problem, since it does not pass this screen, I connect it to my computer and it does not detect it, it has a solution or someone that can help me solve this problem.
Click to expand...
Click to collapse
The same thing happens to me, I can not restore it in any way, I have a "Moto Z2 Force - XT1789-01" new since I got updated android stopped working and I see that.

Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
1 - Download the motorola drivers and install it: motorola-global-es-latam.custhelp.com/app/answers/prod_detail/a_id/81815
2 - Try to enter the "Recovery Mode" from the "Fastboot", then press the "Volume -" key next to the "Power" key for 2 seconds and then execute the "Wipe" option you can choose to delete your information together to the system or separately, I recommend doing everything full if you really do not need the information stored within your device, to restore the official and original rom as it was previously.
Note: In the event that you can not enter "Recovery Mode", do the following:
1 - Download the Android SDK - Platform Tools r27.0.1: keybase.pub/farwayer/arch/mobile/android-sdk-platform-tools-r27.0.1-1-x86_64.pkg.tar.xz
2 - Download the Firmware for your Retail Version: firmware.center/firmware/Motorola/Moto%20Z2%20Force/Stock/NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
3 - Unzip the Rom in a folder on the desktop that is called "Firmware" and inside that same folder unzip the file "Fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll" from the tool "Platform Tools r27.0.1" all the files remain together.
4 - Then copy the path to your directory where you created the "Firmware" folder, for example: C: \ Users \ "TuUser" \ Desktop \ Firmware and paste it into the console.
commands (CMD) always without executing in administrator mode, with the word "cd" above, it should look like this: cd C: \ Users \ "YourUser" \ Desktop \ Firmware
Note: It must be with the cell phone on and connected by USB cable to the computer in the "Fastboot Mode".
5 - You execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Note: If it fails you from the command "fastboot flash boot boot.img" and gives an error like the following:
Executing ". \ Windows \ fastboot.exe -s ZY224GBN8V flash boot boot.img"
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB) ...
OKAY [0.501s]
writing 'boot_a' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished Total time: 0.677s
All devices are flashed
It is because you will have to Unlock the "Bootloader" and that is done as follows:
Note: When you unlock the "Bootloader" you lose the guarantee, so from that moment it is your responsibility to continue or stop here.
1 - Enter the Motorola page to request the deactivation code: accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone % 2Fbootloader% 2Funlock-your-device-b
2 - In the command console (CMD) without entering the administrator mode, copy the same path where you have the files in the folder "Firmware" and the adhere as explained in the previous point so you can execute the following command:
fastboot oem get_unlock_data
3 - Copy the rows of numbers and paste in the motor tool "Data Scrub Tool" so that you combine all the lines in one and you can copy the final code correctly in the box "Can my device be unlocked?" Once done, press the button you confirm the pop-up window and then click on the "I Agree" box and below it appears a button to request the code via email with which you entered the Motorola website.
4 - In CMD, enter the following command:
fastboot oem unlock "Your unlock code that was sent to the mail box"
5 - Download the tool "TWRP - Nash v3.2.1.0 R3": mirrors.lolinet.com/firmware/twrp/nash/
6 - Unzip the iso in the "Firmware" directory and rename it as "Recovery", then install it with the command:
fastboot flash recovery recovery.img
fastboot reboot
7 - Enter the "Fastboot Mode" again and select the option "Recovery Mode" once in search for the option "Wipe" to erase everything that has the device in case you can not find it, type the following commands in CMD:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase carrier
fastboot erase ddr
8 - Then you restart the device and enter "Mode Fastboot" again and execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
9 - With this I should install and operate correctly.
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.

Thank you very much friend I will try to do that tutorial that you say if I can recover my cell phone.
VFArts said:
Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
1 - Download the motorola drivers and install it: motorola-global-es-latam.custhelp.com/app/answers/prod_detail/a_id/81815
2 - Try to enter the "Recovery Mode" from the "Fastboot", then press the "Volume -" key next to the "Power" key for 2 seconds and then execute the "Wipe" option you can choose to delete your information together to the system or separately, I recommend doing everything full if you really do not need the information stored within your device, to restore the official and original rom as it was previously.
Note: In the event that you can not enter "Recovery Mode", do the following:
1 - Download the Android SDK - Platform Tools r27.0.1: keybase.pub/farwayer/arch/mobile/android-sdk-platform-tools-r27.0.1-1-x86_64.pkg.tar.xz
2 - Download the Firmware for your Retail Version: firmware.center/firmware/Motorola/Moto%20Z2%20Force/Stock/NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
3 - Unzip the Rom in a folder on the desktop that is called "Firmware" and inside that same folder unzip the file "Fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll" from the tool "Platform Tools r27.0.1" all the files remain together.
4 - Then copy the path to your directory where you created the "Firmware" folder, for example: C: \ Users \ "TuUser" \ Desktop \ Firmware and paste it into the console.
commands (CMD) always without executing in administrator mode, with the word "cd" above, it should look like this: cd C: \ Users \ "YourUser" \ Desktop \ Firmware
Note: It must be with the cell phone on and connected by USB cable to the computer in the "Fastboot Mode".
5 - You execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Note: If it fails you from the command "fastboot flash boot boot.img" and gives an error like the following:
Executing ". \ Windows \ fastboot.exe -s ZY224GBN8V flash boot boot.img"
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB) ...
OKAY [0.501s]
writing 'boot_a' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished Total time: 0.677s
All devices are flashed
It is because you will have to Unlock the "Bootloader" and that is done as follows:
Note: When you unlock the "Bootloader" you lose the guarantee, so from that moment it is your responsibility to continue or stop here.
1 - Enter the Motorola page to request the deactivation code: accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone % 2Fbootloader% 2Funlock-your-device-b
2 - In the command console (CMD) without entering the administrator mode, copy the same path where you have the files in the folder "Firmware" and the adhere as explained in the previous point so you can execute the following command:
fastboot oem get_unlock_data
3 - Copy the rows of numbers and paste in the motor tool "Data Scrub Tool" so that you combine all the lines in one and you can copy the final code correctly in the box "Can my device be unlocked?" Once done, press the button you confirm the pop-up window and then click on the "I Agree" box and below it appears a button to request the code via email with which you entered the Motorola website.
4 - In CMD, enter the following command:
fastboot oem unlock "Your unlock code that was sent to the mail box"
5 - Download the tool "TWRP - Nash v3.2.1.0 R3": mirrors.lolinet.com/firmware/twrp/nash/
6 - Unzip the iso in the "Firmware" directory and rename it as "Recovery", then install it with the command:
fastboot flash recovery recovery.img
fastboot reboot
7 - Enter the "Fastboot Mode" again and select the option "Recovery Mode" once in search for the option "Wipe" to erase everything that has the device in case you can not find it, type the following commands in CMD:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase carrier
fastboot erase ddr
8 - Then you restart the device and enter "Mode Fastboot" again and execute the following chain of commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp adspo.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
9 - With this I should install and operate correctly.
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.
Click to expand...
Click to collapse

VFArts said:
Note: You can download the tool "SuperSU v2.82" and install using the "Recovery Mode" to be able to have Super User permissions on your device or access "Root" and thereby eliminate the gaps that are predetermined in the firmware as many others privileges.
I hope you have helped, many luck, greetings.
Click to expand...
Click to collapse
SuperSU is no longer being developed. Magisk is the suggested and more reliable root for our phone.
Sent from my Moto Z (2) using XDA Labs

VFArts said:
Well so I'm seeing your firmware is retail, it's easier than my problem, I'll help you, do the following:
I also have the problem of 1789-03. I can not unlock because I need to enable it OEM unlocking' in Android Settings > Developer
"(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options"
But I can not boot into the system !!!!
Please HELPP!!!!
Click to expand...
Click to collapse

Update Pie (December)

Hi all!
I installed PIE using the VPN method in the beginning of the month. Now, the update (about 90mb) was released but I'm getting an error message.
I tried several networks, WiFi or cellular but the error persists.
Does any one has an idea on what I can do? I don't have a working windows computer unfortunately.
Regards!

How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,

Gregor250385 said:
How on earth did you turn on the battery % in the status bar??
Click to expand...
Click to collapse
asking the real questions!

Gregor250385 said:
How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,
Click to expand...
Click to collapse
You can use: https://play.google.com/store/apps/details?id=com.bryancandi.android.uituner
This is what I used and is working without issues.
I'm just not able to update to the lastest version rolled out today. Damn it!

well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.

senntennce said:
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.
Click to expand...
Click to collapse
Well you can try to use vmware workstation and emulate windows, theoretically it would work but dont forget to install the drivers otherwise it wont be recognized.
Edit : platform tools exists also for mac os.

reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though

DrEzkimo said:
reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though
Click to expand...
Click to collapse
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!

senntennce said:
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!
Click to expand...
Click to collapse
Just do what i told it will be fine, as i said there is a version of platform tools for mac os, if you need further help i ll be here.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.

Does this version have the bug as vpn version? For example flash of screen (normale/black)?

croccio said:
Does this version have the bug as vpn version? For example flash of screen (normale/black)?
Click to expand...
Click to collapse
Nope, works perfectly, 0 bugs.

i have problems with wifi
can't connect to any of my saved wifi
tried to reset wifi twice, but it doesn't work

Hakkinan said:
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.
Click to expand...
Click to collapse
I'm currently downloading those files.
The commands that I need will be:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Correct?
Thanks

Well, for my case i would rather remove everey thing and start from scratch for a fresh start with only One command and zero risk, if you get the same result with fastbooting go ahead.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
XIaomi specifically warns you about NOT reverting to Oreo once you are on Pie.

After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Edit: Yeah, after reading some more, it seems that it is required to have the boot loader unlocked and I don't have it. Bummer.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
I'm not sure about MacOS (since i don't have one) but in Windows/Linux this happens when you use an older version of fastboot.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
Since your windows is down, can you try it on a virtual machine (vmware workstation) ?

The System has been destroyed - only fastboot possible

Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant

Blasmuskant said:
Hello,
I bricked my Redmi Note 8T and I have no idea how to save my phone!
What did I do?
I unlocked my phone with XiaomiTool V2 and added Magisk, installed TWRP and trieed to add LineageOS.
So I tried to restart but the system stocked in a "boot - shutdown - boot - shutdown..."
I read in a description, that I have to delete in TWRP-mode some folders in WIPE so I deleted "System", "Data", "Cache", and maybe some other folders! I'm so stupid!
So there is only "The System has been destroyed", after around 30 seconds the system starts again and the bad massage comes again...
It is just possible to start the fastboot mode!
So I tried again to flash and boot TWRP:
sudo fastboot flash recovery twrp.img
target reported max download size of 804274176 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.617s]
writing 'recovery'...
OKAY [ 0.349s]
finished. total time: 1.967s
sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.615s]
booting...
FAILED (status read failed (No such device))
finished. total time: 37.120s
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
Doesn't sound so bad. And of you had searched the forum before panic posting, you would have easily found at least 3 similar threads already started.
Not knowing what you had wiped from twrp before, leaves the best option for you is to flash the factory fastboot ROM, and then start over.
There is a thread here about fastboot ROM i beleive.

just miflash

Blasmuskant said:
Afterwards the system says again "The System has been destroyed".
So now I don't have any idea to save my phone!
Please help me! I trust in you!
My OS on the PC is Ubuntu for your information...
Best wishes
De Blasmuskant
Click to expand...
Click to collapse
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from here or here..
then download latest platform tools.
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.

Thank you for your fast answers! I tried already the search function but it seemed to me beeing different problems!
wsdyleon said:
just miflash
Click to expand...
Click to collapse
How can I do it in fastboot mode with Linux?
the_weird_aquarian said:
in fastboot rom there must be a file vbmeta.img....if you don't want to download the fastboot rom then download vbmeta.img from ...
then download ...
extract the plaform tools zip...copy vbmeta.img in this folder,open cmd/terminal in this folder path and flash vbmeta with phone in fastboot mode by this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after this flash recovery.
Click to expand...
Click to collapse
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?

Blasmuskant said:
I tried it with the vbmeta.img from the fastboot Redmi Note 8 – Global Stable ROM (V11.0.9.0.PCOMIXM | MIUI 11 | Android 9.0) and the platform-tools for linux from xiaomifirmware.com.
sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
< waiting for any device >
On the phone then is "Press any key to shutdown"
After trying again I got:
target didn't report max-download-size
sending 'vbmeta' (4 KB)...
But then nothing happens...
What is wrong?
Click to expand...
Click to collapse
Was your phone connected in fastboot?

the_weird_aquarian said:
Was your phone connected in fastboot?
Click to expand...
Click to collapse
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...

Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Is it working now? Why don't you try flashing the stock firmware again?

Blasmuskant said:
Yes, it has been connected in fastboot mode... I pressed "Power-On" and "Volume-Down" before and on screen it says FASTBOOT...
Click to expand...
Click to collapse
Download the latest platform tools and try again once

It works!
[email protected] said:
Is it working now? Why don't you try flashing the stock firmware again?
Click to expand...
Click to collapse
It worked, I installed the Stock recovery and then TWRP (all with fastboot) and so it was possible for me to install LineageOS!
Thank you very much for your support!

Question For those who have flashed International ROM but NFC not working

PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone

Ehh it works, thanks brother!

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
What Rom are you using?
Do you have any bugs on it?
Android auto works?

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
Is it possible to use this method to change touchscreen drivers? Do you know where it is stored at?
I was having a weird touch screen problem with virtual buttons with an international modified Rom and this touchscreen problem was not present on Chinese stock Rom...

a723356 said:
PS: I know some of the linux thing, but I have no experience in building an Android ROM. Any suggestion and discussion are welcomed
1. Make sure you are on the CN ROM. If not, revert to it.
2. On your CN ROM with magisk/root access, run
Code:
dd if=/dev/block/mapper/vendor_a of=/sdcard/vendor.img
this is to dump the vendor partition where the NFC drivers locate. use vendor_b instead if you are in the b_slot
3. Copy your dumped vendor.img from your phone to your computer with fastboot env.
4. Now flash your internation ROM: AP only
5. run
Code:
fastboot reboot fastboot
get your phone into fastbootd
6.
Code:
fastboot erase vendor_a
fastboot flash vendor_a <path of your vendor.img dumped from CN ROM>
7. reboot to fastboot, run fastboot erase userdata in case the userdata is encrypted
8. restart your phone
Click to expand...
Click to collapse
what img files are excluded in AP flashing process?

doesnt worked for me

How big should the file be "vendor.img"? My has 1,13GB
I try flash it, but get error.
Code:
C:\Users\snego\Downloads\tools_r33.0.2-windows>fastboot erase vendor_a
Erasing 'vendor_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\Users\snego\Downloads\tools_r33.0.2-windows>fastboot flash vendor_a vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: '')
fastboot: error: Command failed
1. Go in fastboot mode
2. fastboot reboot fastboot
3. flash vendor in fastbootD mode.
but still it didn't help. phone won't boot after vendor.img flash