Database Develop

Formatted Phone w/ No Nandroid

Last night, my phone was running slow so I rebooted my phone. My phone started bootlooping (stayed in the bootloader warning screen).
Here's where it gets weird: I went into TWRP and tried a bunch of different solutions. I tried to create a nandroid and a bunch of error messages popped up like "E: unable to /mount". I tried factory reset and same error messages.
I was worried the bootloop would occur again so I pressed format data and without thinking, formatted my entire card.
Now I have a phone with no system, no backup, but still in the TWRP screen. Without doing more damage, where do I go from here?
Moto X 2014 Pure Edition with bootloader unlocked.

Looks like you're going to have to flash the factory images and start fresh.
Sent from my XT1095 using Tapatalk

Thanks for the quick reply. Can you guide me towards doing that?

You could go the factory image route (just google Motorola Factory Images and it'll be the first result. You need a motorola account to access them).
You can also boot into TWRP and transfer a ROM over via ADB if you want to stick with the custom ROMs. Just boot into TWRP and connect to your computer, then adb push the ROM file.

This is the error message I get when I tried to push a zip to my /sdcard directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says it's a "Read-only file system".

You would unzip that file to get to the sparsechunks and then you would:
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
DocDroid said:
This is the error message I get when I tried to push a zip to my /sdcard directory:
It says it's a "Read-only file system".
Click to expand...
Click to collapse

I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.

I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.
d33dvb said:
You would unzip that file to get to the sparsechunks and then you would:
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Click to expand...
Click to collapse

DocDroid said:
I extracted the zip file into the same folder. I copied your first line of command and this has been my screen for the past 15 minutes:
Should it take that long? As a note, all the files you mentioned are there.
Click to expand...
Click to collapse
Are you trying to flash those in recovery? You need to be in fastboot (bootloader) mode.
Sent from my XT1095 using Tapatalk

dustin_b said:
Are you trying to flash those in recovery? You need to be in fastboot (bootloader) mode.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The rabbit hole goes deeper. I'm in bootloader mode, copy and paste the first line of command, and here's the new error:

Is your bootloader unlocked?

Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
---------- Post added at 04:21 PM ---------- Previous post was at 04:21 PM ----------
d33dvb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
It has to be since he had twrp.
Sent from my XT1095 using Tapatalk

d33dvb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, unlocked bootloader. Motorola Device Manager tells me my phone's current version is "22.21.11.victara_tmo.tmo.en.us" and I was running Lollipop 5.0 before it went beserk yesterday.
I downloaded the image file from http://www.graffixnyc.com/motox.php under the title "Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip."
I honestly don't know what is wrong!!

dustin_b said:
Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
Just tried that. Powered off phone, held onto power button + down, entered bootloader mode, inputted first line of command, and still the same error message.
Click to expand...
Click to collapse

DocDroid said:
dustin_b said:
Did you reboot into bootloader from twrp? If so, power off there phone and not into fastboot that way. Then try it.
Sent from my XT1095 using Tapatalk
Just tried that. Powered off phone, held onto power button + down, entered bootloader mode, inputted first line of command, and still the same error message.
Click to expand...
Click to collapse
Do you have fastboot installed? If so, try using it instead of mfastboot. I had a problem like that once but I really don't know what fixed it. That's about the only other suggestion I have.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse

dustin_b said:
DocDroid said:
Do you have fastboot installed? If so, try using it instead of mfastboot. I had a problem like that once but I really don't know what fixed it. That's about the only other suggestion I have.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
- I installed Minimal ADB and Fastboot tool found here.
- I placed the zip file in the "Minimal ADB and Fastboot" folder.
- I took all the commands from above and inputted.
- Error message: "Boot up failed. Invalid boot image header!"
HELP!
Click to expand...
Click to collapse

New development:
I flashed "TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip" using the commands given with success!
Figuring that this is it, I pressed "normal startup" and my phone is once again stuck in the "Warning Bootloader unlocked" screen. Has not gone to the Moto world animation screen yet.

Because u hav wiped ur entire os widout nandroid backup..u will hav to flash a rom(stock or custom..ur choice) again..Ensure u hav an unlocked bootloader..Download a rom frm the internet that suits ur device and place it on the root of sd card..then boot into twrp..wipe data and cache..click install and find ur image and click it..the rom will get flashed to ur device..
Sent from my Micromax A110 using XDA Free mobile app

REDswapnil said:
Because u hav wiped ur entire os widout nandroid backup..u will hav to flash a rom(stock or custom..ur choice) again..Ensure u hav an unlocked bootloader..Download a rom frm the internet that suits ur device and place it on the root of sd card..then boot into twrp..wipe data and cache..click install and find ur image and click it..the rom will get flashed to ur device..
Sent from my Micromax A110 using XDA Free mobile app
Click to expand...
Click to collapse
By attempting to flash that stock image above, I lost TWRP and now on stock recovery. I can only access bootloader now. Which file should I try to flash via fastboot? That seems to be my only solution.

DocDroid said:
Yes, unlocked bootloader. Motorola Device Manager tells me my phone's current version is "22.21.11.victara_tmo.tmo.en.us" and I was running Lollipop 5.0 before it went beserk yesterday.
I downloaded the image file from http://www.graffixnyc.com/motox.php under the title "Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip."
I honestly don't know what is wrong!!
Click to expand...
Click to collapse
Why did you download it from there rather than from Motorola's official site? I wouldn't feel confident that the images are actually legitimate. Download them from motorola:
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
From that link click Get recovery images here and download them from the official source.

Android OS gone, unable to mount any partition, etc. Need help.

So I don't know what to do at this point. I will try to provide as much info as I can for you guys to help me out. I bought the Verizon 2014 Moto X variant off Swappa new. The phone was new, but old. It was manufactured in 2014 and upon first boot, it still had KitKat installed. I OTA'd all the updates before unlocking the bootloader from Motorola's website. After unlocking the bootloader, I tried flash TWRP recovery via fastboot. It didn't work - I got a pink message line on the output that I don't remember what it said. I read that there were some issues installing recovery for VZW (?) so using flashify was my other option. So I then rooted the phone and used flashify to install TWRP. It worked. After that, I flashed a 2014 MM Pure Edition rom. It booted fine, but no signal. Yes, I forgot that it doesn't support CDMA, so I then went tried to flash CM13. Today, I started experiencing battery drain on radio and wifi so I tried to flash the official firmware of 5.1 VZW Victara variant. Fastboot and drivers are running fine and fastboot recognizes the phone. So I flashed everything, booted up, and...nothing. Every time I tried to reflash the firmware, I boot to a blinking No Command dead andy screen. Guess recovery wasn't installed? It just kept bootlooping. Out of desperation, I went to see if TWRP worked - it did. Now I ADB pushed the CM13 rom files on my phone to flash. Unfortunately, every time I try to flash anything, every partition is unable to be mounted. I can't factory reset, flash, nothing. Every time I try to wipe, one of the errors is, 'Failed to mount '/data' (Invalid Argument)'. Now at this point, this is where I'm stuck. I still have the bootloader/fastboot, a recovery, but no OS and I can't flash anything. Fastbooting the firmwares won't go through to boot. Can anyone help me on this? I will provide answers to any questions you have. Thanks.
EDIT: I tried to turn off the phone to prevent the phone from dying but I can't even do that. Tried to turn it off via TWRP but it just reboots to TWRP. I have to keep it plugged in. Sigh.

DroidOnRoids said:
So I don't know what to do at this point. I will try to provide as much info as I can for you guys to help me out. I bought the Verizon 2014 Moto X variant off Swappa new. The phone was new, but old. It was manufactured in 2014 and upon first boot, it still had KitKat installed. I OTA'd all the updates before unlocking the bootloader from Motorola's website. After unlocking the bootloader, I tried flash TWRP recovery via fastboot. It didn't work - I got a pink message line on the output that I don't remember what it said. I read that there were some issues installing recovery for VZW (?) so using flashify was my other option. So I then rooted the phone and used flashify to install TWRP. It worked. After that, I flashed a 2014 MM Pure Edition rom. It booted fine, but no signal. Yes, I forgot that it doesn't support CDMA, so I then went tried to flash CM13. Today, I started experiencing battery drain on radio and wifi so I tried to flash the official firmware of 5.1 VZW Victara variant. Fastboot and drivers are running fine and fastboot recognizes the phone. So I flashed everything, booted up, and...nothing. Every time I tried to reflash the firmware, I boot to a blinking No Command dead andy screen. Guess recovery wasn't installed? It just kept bootlooping. Out of desperation, I went to see if TWRP worked - it did. Now I ADB pushed the CM13 rom files on my phone to flash. Unfortunately, every time I try to flash anything, every partition is unable to be mounted. I can't factory reset, flash, nothing. Every time I try to wipe, one of the errors is, 'Failed to mount '/data' (Invalid Argument)'. Now at this point, this is where I'm stuck. I still have the bootloader/fastboot, a recovery, but no OS and I can't flash anything. Fastbooting the firmwares won't go through to boot. Can anyone help me on this? I will provide answers to any questions you have. Thanks.
EDIT: I tried to turn off the phone to prevent the phone from dying but I can't even do that. Tried to turn it off via TWRP but it just reboots to TWRP. I have to keep it plugged in. Sigh.
Click to expand...
Click to collapse
So you have the full stock firmware 5.1 for Verizon XT1096, like the one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Can you try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
TWRP 3.0 seems to be causing problems, maybe corrupting partitions, stick to 2.8.7.1 or earlier.
http://www.invisiblek.org/
Maybe we can try RSD Lite...

Gus Ghanem said:
So you have the full stock firmware 5.1 for Verizon XT1096, like the one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Can you try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
TWRP 3.0 seems to be causing problems, maybe corrupting partitions, stick to 2.8.7.1 or earlier.
http://www.invisiblek.org/
Maybe we can try RSD Lite...
Click to expand...
Click to collapse
I did not get the file from there, but instead got it from AFH. As for the 2 fastboot commands, what should I do with them? They flashed fine when I was putting them in fastboot earlier. As for TWRP, I will flash to 2.8.7.1.
As for RSD Lite, I am running Windows 10 and several versions I have tried will not recognize the phone at all. I'm 95% sure the drivers are in OK status and I am using the OEM cable.

DroidOnRoids said:
I did not get the file from there, but instead got it from AFH. As for the 2 fastboot commands, what should I do with them? They flashed fine when I was putting them in fastboot earlier. As for TWRP, I will flash to 2.8.7.1.
As for RSD Lite, I am running Windows 10 and several versions I have tried will not recognize the phone at all. I'm 95% sure the drivers are in OK status and I am using the OEM cable.
Click to expand...
Click to collapse
I downloaded your firmware just to check the number of files, and the flashfile.xml, and it's exactly like this:
VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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

Gus Ghanem said:
I downloaded your firmware just to check the number of files, and the flashfile.xml, and it's exactly like this:
VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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
Click to expand...
Click to collapse
I appreciate you providing help so far. I downloaded the firmware you linked, fastbooted line for line, rebooted, bootloader unlock warning pops up, then the next boot sequence is just the blinking dead andy No Command logo that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm still stuck. I'm going to flash the 2.x.x TWRP version again. But that's all I'll be able to get right now. Still not able to get an OS installed.

DroidOnRoids said:
I appreciate you providing help so far. I downloaded the firmware you linked, fastbooted line for line, rebooted, bootloader unlock warning pops up, then the next boot sequence is just the blinking dead andy No Command logo that looks like this:
I'm still stuck. I'm going to flash the 2.x.x TWRP version again. But that's all I'll be able to get right now. Still not able to get an OS installed.
Click to expand...
Click to collapse
Any errors on the phone during fastbooting firmware files, like "downgrading" etc.
I hope TWRP 2.x will allow you to flash CM.

UPDATE: So I made a little progress. There was a problem mounting and this thread helped with that: http://forum.xda-developers.com/showthread.php?t=2683787
Now I can wipe data, factory reset, flash, etc. in TWRP v2.8.7.1. But when I flash a rom, I reboot system and it boots back to recovery. WTF. Ugh.
EDIT 2: Sad news. Based off this thread, http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147, looks like I FUBAR'd the phone. Unfortunate that this phone isn't like a Nexus.

its the phone will reboot back to TWRP event you restore backup file on TWRP ?
did you try flash custom rom from TWRP?
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
DroidOnRoids said:
UPDATE: So I made a little progress. There was a problem mounting and this thread helped with that: http://forum.xda-developers.com/showthread.php?t=2683787
Now I can wipe data, factory reset, flash, etc. in TWRP v2.8.7.1. But when I flash a rom, I reboot system and it boots back to recovery. WTF. Ugh.
EDIT 2: Sad news. Based off this thread, http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147, looks like I FUBAR'd the phone. Unfortunate that this phone isn't like a Nexus.
Click to expand...
Click to collapse
its the phone will reboot back to TWRP event you restore backup file on TWRP ?
did you try flash custom rom from TWRP?

Android O (All variants)

Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk

already flashed retail O on Sprint and now looking for root solution

HugeUFO said:
already flashed retail O on Sprint and now looking for root solution
Click to expand...
Click to collapse
Did flashing magisk not work?

donjuro said:
Did flashing magisk not work?
Click to expand...
Click to collapse
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言

donjuro said:
I'll post a couple tutorials tomorrow
Click to expand...
Click to collapse
Great, looking forward to it.

HugeUFO said:
nope, I never tried Magisk before. And a complete backup needs root access, but to gain root access I need Magisk, which recommends a backup[emoji23]
通过我的 Moto Z (2) 上的 Tapatalk发言
Click to expand...
Click to collapse
You don't need root access to backup with twrp

donjuro said:
You don't need root access to backup with twrp
Click to expand...
Click to collapse
Oh thanks, I will try to flash a twrp to backup.

donjuro Please come back to as if you will find moment. We are still waiting.

Hey guys, sorry I've been gone for so long. Life really kicks your ass sometimes
Anyways, it looks like just about every carrier is on 8.0 now except Sprint, but if you're on another carrier yet you still haven't been upgraded you could try this too.
So basically all you have to do is download NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from one of these two mirrors.
https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
https://mirrors.lolinet.com/firmware/moto/nash/official/
Unpackage the zip file, and inside the folder create a flashall.bat, here is what you will put in the bat file
Code:
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 flash bluetooth BTFM.bin
fastboot flash dsp adspso.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 cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Save it, put your phone in fastboot mode, run it, and that should be it. You might want to make a backup of any valuable files first though as this WILL erase everything and will start you from scratch!
For those of you wanting to keep your carrier specific features, you can use your carrier specific files from any of these mirrors, but for stability purposes I highly recommend using the RETAIL version.

robdevil said:
donjuro Please come back to as if you will find moment. We are still waiting.
Click to expand...
Click to collapse
what is the issue you are having?

thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again

ilovemeow said:
thanks mate, and wanna ask for twrp backup issue, anyone have issue for restore from twrp,
i've got bootloop after TWRP restore, (was working before backup)
once android O stable, I can upgrade to O asap, thanks again
Click to expand...
Click to collapse
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.

JAWheat411 said:
If it is just restarting into TWRP over and over, you might just need to switch to a different slot. It is there in the reboot area of TWRP.
Click to expand...
Click to collapse
hmm, not really restarting into twrp,
i pass the twrp, reboot itself before "hellomoto" screen appear

Are you able to reflash the stock boot image in bootloader?

Help Please.
donjuro said:
Hey guys, for those of you who have bricked your phone by upgrading to Oreo then tried downgrading to nougat, I may have a fix for you. Also news that Android O can be installed on Sprint (and possibly locked bootloader variants too). I'm going to sleep now, I'll post a couple tutorials tomorrow when I get home from work but I wanted to give you guys a little sneak peak of what I've discovered.
Edit: also, this is running buttery smooth for me. Which leads to believe those of you having performance issues with O it's probably due to some carrier apps/features, which would be in the OEM partition. Side note, this is a retail rom, which means no carrier bloat/features. This is as if you were to buy it unlocked straight from Motorola. This also means I have no VoWiFi on Sprint. If anyone could find a way to implement this in O that would be awesome.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help

AsapJuno said:
So i have a T-Mobile variant and I attempted to root and got a bootloop. SO i surfed the web and found this. Downloaded firmware from the 3nd site you linked, did everything else as well and I don't have wifi or mobile data. Please help
Click to expand...
Click to collapse
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk

donjuro said:
What version does your baseband say?
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It says unknown now

AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Well, you're kind of in for a bad time now... The "official" tmobile oreo zip that's out there flashes fine but then you end up with no baseband.
@MootNewt made a zip here: https://forum.xda-developers.com/z2-force/help/t-mobile-oreo-flashall-t3755086/post75810018
that will flash to the latest tmobile oreo (with feb update) but you'll end up not passing safetynet, even with Magisk.
You will have root via Magisk, though, so there's that.
This is where I am right now. :/

AsapJuno said:
It says unknown now
Click to expand...
Click to collapse
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.

JAWheat411 said:
Also if it helps here is a T-Mobile flash all to the latest firmware. https://drive.google.com/file/d/153BdClEOK3ZzpgiM37Ti4Y8lkyXPcz0S/view?usp=sharing
Just run the flash all bat file while your phone is in bootloader mode. This will wipe everything, just a fair warning. I am using this now. No problems with safety net here.
Click to expand...
Click to collapse
Are you saying that it's got the 27.1 update and it passes safetynet?
e: AND it doesn't eat your baseband?

Brick my MI A2

After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?

https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188

minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)

Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.

use ./fastboot flashing unlock_critical

Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.

djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.

Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.

djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.

meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?

Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.

Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!

people try:
1- Another usb port
2- Another usb cable
3- Another PC

I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs

woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?

Stock Pie on RETCN (XT1789-05) Z2 Force (Hybrid of RETCN Oreo, RETEU Oreo and RETEU Pie roms)

I will describe how I managed to flash PIE RETEU_9.0 version on Chinese RETCN XT1589-05 with stock Oreo. It is a triple hybrid ROM (better than just Hybrid ) In short I installed bootloader part from RETCN 8.0, baseband from RETEU 8.0 and system from RETEU 9.0. Detailed description below.
We will need to download 2 firmwares: RETEU_DS_8.0.0_OPXS27.109-34-21 and RETEU_DS_9.0_PPX29.159-24. Optionally download RETCN_8.0.0_OCX27.138-29-3
first enter to bootloader:
adb reboot bootloader
[OPTIONAL] we will flash flashall.bat included in RETCN_8.0 (I did that, because I've recovered from brick ), You can also skip this point or just flash bootloader part from RETCN_8.0:
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
Then flash Baseband part from RETEU_8.0. DO NOT FLASH baseband from RETEU 9.0. otherwise there is a risk that you will lost your radio/bt/wifi (at least on Sprint/Verizon version). I suspect it should work on retcn version, but I'm not going to try.
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
At the end we flash System part from RETEU_9.0
fastboot flash boot boot.img
flashing boot.img most propably will fail. Do not panic, this is normal. Solution is below.
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 system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
OPTIONAL: I have wiped oem partition in TWRP without impact on system, so you can skip this line if you want (but you must wipe also if you skip)
If flashing boot.img via fastboot fails, flash it through TWRP.
Boot to TWRP
fastboot boot twrp.img
Transfer boot.img to internal memory, select Install, select Install Image, and select boot.img from SD card. When asked, select boot.
At the end wipe user data (You can do it via TWRP)
fastboot -w
And reboot
fastboot reboot
Now You have fully working PIE on your XT1589-05 RETCN I haven't noticed any problems with the phone. Radio/baseband (wifi, bluetooth, calling and network) works flawlessly. What's more, on factory firmware during call network was drop from 4G / LTE+ to 2G / E, now it drops only to 3G / H. If You want, You can also skip flashing baseband part, but I've noticed, that baseband from RETEU_8.0 works better than from RETCN_8.0 (I've tried both) . It has less impact on battery and it won't drops to 2G during call (at least in Europe).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do you know if the rom RETEU_DS_9.0_PPX29.159-24 still available somewhere?

uzi74 said:
Do you know if the rom RETEU_DS_9.0_PPX29.159-24 still available somewhere?
Click to expand...
Click to collapse
Lolinet moves fw for older devices to _obsolete_ directory.
BTW You can flash just RETEU or RETAPAC fw instead hybrid rom.