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?

[XT1804] i Was Able to Lock Bootloader on NPSS26.116-26-4- Indian Version

I tried this version of rom and i was able to relock my bootloader
SANDERS_NPSS26.116-45-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Bases on October patch See the attachment
Link to the Rom:
https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/
{
"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"
}
Commands are Same as before used
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
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 system system.img_sparsechunk.5
fastboot flash boot boot.img
fastboot oem lock
The Reflash full firmware
-Hope will work for u too
HIt thanks if helped

yograjfire18 said:
I tried this version of rom and i was able to relock my bootloader
SANDERS_NPSS26.116-45-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Commands are Same as before used
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
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 system system.img_sparsechunk.5
fastboot flash boot boot.img
fastboot oem lock
The Reflash full firmware
-Hope will work for u too
HIt thanks if helped
Click to expand...
Click to collapse
Where did u get the firmware

navnit75 said:
Where did u get the firmware
Click to expand...
Click to collapse
added to the op

yograjfire18 said:
added to the op
Click to expand...
Click to collapse
Yeah bootloader successfully relocked.

Hey can you tell me that is it the latest build I mean Oct. Patched build
Bcoz I updated it but now I flashed twrp & custom ROM
and trying to flash stock ROM which is the older build it didn't flashed because it was written as system is downgrading and failed

yograjfire18 said:
I tried this version of rom and i was able to relock my bootloader
SANDERS_NPSS26.116-45-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Bases on October patch See the attachment
Link to the Rom:
https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/
View attachment 4366322
Commands are Same as before used
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
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 system system.img_sparsechunk.5
fastboot flash boot boot.img
fastboot oem lock
The Reflash full firmware
-Hope will work for u too
HIt thanks if helped
Click to expand...
Click to collapse
Thanks a lot! It really helped

Akkikuntal said:
Hey can you tell me that is it the latest build I mean Oct. Patched build
Bcoz I updated it but now I flashed twrp & custom ROM
and trying to flash stock ROM which is the older build it didn't flashed because it was written as system is downgrading and failed
Click to expand...
Click to collapse
Did u wiped off the system and data partition before doing that???
Sometimes a complete format would be great enough to ensure '0' errors

thippu46 said:
Did u wiped off the system and data partition before doing that???
Sometimes a complete format would be great enough to ensure '0' errors
Click to expand...
Click to collapse
nthng, i have written everything in the op, will work for everyone

I flashed this firmware and was able to lock the bootloader... But will we get December patch ota because I am not getting ota with this rom... If I want ota then which ROM should I flash....

Kakshay0981 said:
I flashed this firmware and was able to lock the bootloader... But will we get December patch ota because I am not getting ota with this rom... If I want ota then which ROM should I flash....
Click to expand...
Click to collapse
u need to unlock bootloader and flash its own stock rom NPSS26.116-26, but it won't lock bootloader

Need Moto g5s plus device drivers, an any one share

Thank you, just did this to the XT1806 and the bootloader locked. Now I can get ota updates when they eventually come

how can u lock bootloader i have same model xt 1804 but its not work

Worked for me! Can we still receive OTA's after using this?

William1020000 said:
Worked for me! Can we still receive OTA's after using this?
Click to expand...
Click to collapse
You'll only receive OTA updates if you've flashed with the correct firmware for your software channel. Whilst you can flash and lock with other region's firmwares, your device may not be recognised by the Motorola servers for OTA updates, which means you may have to manually update.

Doesn't work
bootloader: slot count not found
slot suffixes not found error
still required signed boot.img
error it doesn't work please help

navnit75 said:
Yeah bootloader successfully relocked.
Click to expand...
Click to collapse
Were you able to get the imei?? And signals?
Because i had lost it when i tried with another thread. And recoverd from validus rom.
Thanks

Can you list the full commands

Why your baseband version is different and build number is same as latest one and security patch level are also different

William1020000 said:
Worked for me! Can we still receive OTA's after using this?
Click to expand...
Click to collapse
Yes definitely!!!!

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?

Bricked phone flashing twrp 3.3 on p20 pro. Don't know what to do.

Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.

androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk

zencooler said:
Did you try to recover your phone using HiSuite? Boot into fastboot mode and then repair phone via HiSuite. This will flash you back to latest official firmware for your model. Please be aware you will lose your data.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for replying. I've just tried that and it says 'Your system is not supported for recovery'.

Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka

cielik said:
Maybe try to flash via host otg.
Wysłane z mojego CLT-L29 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....

androidyeah... said:
Thanks, I've read about that method too, but the only download I have doesnt have a 'dload' folder when i extract it as required in this post (4 posts down)? Its the b270 firmware.
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085
I've just bought a pass with funky hauwei only to find out the tool doesn't work anymore
Some guy there suggested 'flashing every partition from the update.app and seeing if anything changes. Some will flash and others will fail but it’s a good first step'. I don't know what that means exactly, is that everything in the update.app? He hasn't replied yet....
Click to expand...
Click to collapse
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:

Try to use the Flash TOOL of this post, it always works with me.
https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964

androidyeah... said:
Hi,
I have bricked my phone (CLT-L29 9.0.0.270(C432) by trying to flash twrp 3.3 using the app from the app store. I had downloaded the
twrp-3.3.0-1-charlotte.img and installed it using the app. When I rebooted the phone i got a white screen, saying 'please update system again', func no:11 (recovery image), error no: 2 (load failed!).
I have since tried the following:
I have extracted the recovery ramdisk from the update (9.270) file and flashed that using fastboot flash recovery_ramdisk RECOVERY RAMDIS.img. This hasn't worked, ive also flashed twrp versions. Ive reflashed the system.img.
Erecovery works but gets an error when looking to download the latest version, and factory reset wont work because it returns the original error at boot. It is still oem unlocked. I have the update 9.270 and can extract whatever files are necessary to flash using fastboot, but don't know which ones or where to flash.
I've just spent 5 hours on xda and google trying to fix things but im getting nowhere. I would really appreciate any help or advice on where to go from here. I'll provide any info needed.
sincerely
In Trouble.
Click to expand...
Click to collapse
Try to use OTG dload method.
If you need firmware and help tell me!

I had this problem on my EML-L29, tjis helped me:
factory reset
wipe cache
fastboot erase system
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot

Yeah, similar to what I had to do. Factory reset wasn't possible for me, but flashing partitions worked.

Bricked P20 Pro
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.

Wrong section. Can this be moved please.
I thought there was a new ROM thread..

Rustyrobotguy said:
I also managed to brick my phone flashing twrp.
except I can't access adb or fastboot now.
Not really sure how to go from here to restore my phone.
Click to expand...
Click to collapse
You can always go into fastboot mode in emergency mode.
Just connect the phone to PC via USB cable and then press power key + Volume Down.
It will bring you into Fastboot Emergency.
Then you can play with fastboot commands.
I recommend you to extract RECOVERY_RAMDIS.img from UPDATE.APP (you can get it from update.zip file for your firmware) into a folder that keeps your fastboot exe file. Then do following command on your PC:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
It will give you stock recovery.
Then you can do command:
fastboot reboot
Immediately after this command disconnect USB cable and press Volume Up key.
On recovery you can do wiping your data partition and don't he factory reset.
If it not help and you are still on boot loop you can go again into fastboot emergency mode and do fastboot command:
fastboot -w
This will reformat your data partition and after this your phone will boot into erecovery to do factory reset again. It should help you to bring your phone into live.
Regards.
Sent from my SM-N960F via Tapatalk

androidyeah... said:
I have just spent my day off trying to fix this phone, never again!! I finally found a fix from this post
https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085/page11#post79395575
I flashed cache, kernel, cust and system images from the update.app file and rebooted and the phone came back up good as new. Thanks for the replies, maybe this might help someone else in a simialar boat sometime. :victory:
Click to expand...
Click to collapse
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s

thoughtless22 said:
How were you able to extract files from the update.app?
I'm using Huawei Update Extractor 0.9.9.5 (and 0.9.9.3) and I keep getting error: "Recovery_ramdisk.img: Invalid header crc - Expected:11007 Got 48874"
Update:
I figured out how to extract the files, but every time I try any fastboot commands I keep getting the below error, any ideas??
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 1.696s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
Finished. Total time: 1.729s
Click to expand...
Click to collapse
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk

zencooler said:
Bootloader must be unlocked. Only then you can flash recovery.
But be careful and do not try to flash Oreo rom over the Pie because you can definitely brick your phone (even if you read somewhere that it's possible).
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?

thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Same Problem for me. cant find any way to get this to work.. my Phone is bricked 2 month now i miss it lol
does anyone have a Solution for 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"
}

thoughtless22 said:
Thanks for the reply!
My phone is unlocked, but it shows FRP Lock, that seems to be the issue.
Any ideas how to unlock FRP from fastboot?
Click to expand...
Click to collapse
Try thoes command in fastboot:
HTML:
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
fastboot oem get-build-number
if it returns something weird, then you are fvcked up.
mine messed up once, I had to get to Service Center to replace the motherboard.
Maybe, now there is some 3rd party way can save you phone, I don't know.