As the title says, I have no recovery and can't seem to restore the stock recovery. Also, when I boot/reboot the phone, it goes to fastboot mode. Then if I select START, it will boot to the system.
I purchased this phone used and the bootloader was already unlocked. I installed TWRP, rooted it and set it up. When I put my sim in, I could send & receive text messages and mms messages, but I was unable to talk or hear anything while on a voice call. The call is placed and/or received fine. However, once connected, I cannot hear anything nor can anyone hear me.
I want to return for a refund and have restored to factory per this guide. (the problem persists). However, I do not have a recovery. Flashing the stock recovery thru ADB appears to work but trying to boot to it goes to fastboot mode. I cannot boot/reboot the phone without it going to fastboot, then I have to select START to boot to the system. If I cannot correct these problems I will not be able to return the phone...and I can't use it as is because of the phone issue.
Thanks...and help!
Did the phone work fine when you got it?
Sent from my Moto G6 Plus using Tapatalk
Relock-it
Remember you need root to do this and usb-debugging and OEM-unlock enabled in syste settings
Download firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
and assuming you know were to extract it to, run this command:
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 dspso.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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
fastboot oem lock
fastboot oem lock
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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear
Xplorer4x4 said:
Did the phone work fine when you got it?
Click to expand...
Click to collapse
Booting up and recovery...yes.
xjunior said:
RELOCK IT
Click to expand...
Click to collapse
What will that do for me? I still don't have a recovery.
xjunior said:
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot
Click to expand...
Click to collapse
I don't understand this. How do I erase fastboot reboot? It's a command to reboot.
if you use the firmware from the guide you show in the first post is probably not the right one for your device, I have exactly same model and took me a wile to figure out how to factory reset and relock it.
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command, line by line not all at once like the first part.
this will bring you device back to factory and relock the bootloader ,
xjunior said:
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command line by line .
this will bring you device back to factory and relock the bootloader ,
Click to expand...
Click to collapse
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
mn1968 said:
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
Click to expand...
Click to collapse
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
xjunior said:
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
Click to expand...
Click to collapse
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
My pleasure
mn1968 said:
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
Click to expand...
Click to collapse
After reflashing stock with OPS27.82-72 (came with OPS27.82-19-4), the phone now actually works too. Very weird. I may have/want to keep the phone now.
Related
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Speedy712 said:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Click to expand...
Click to collapse
So you have the Motorola USB drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Recent versions of ADB/Fastboot.
Latest stock firmware:
firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1096/
Probably VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Extract the firmware and put the 4 ADB/Fastboot files in the folder with the firmware files.
Boot into Bootloader Mode and connect the phone, make sure the phone says "connected..."
Shift + right-click inside that folder, Open command window here... Paste these commands, BUT CHECK THE NUMBER of sparsechunks your firmware has:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Speedy712 said:
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Click to expand...
Click to collapse
You're welcome, glad it worked!
If you want to try custom roms again, I've been using TWRP 3.0.2-1 and it seems to have no issues so far (and I'm running the latest CM Nightlies).
Gus Ghanem said:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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
Click to expand...
Click to collapse
so with this method you dont have to use the motofastboot?
fakieskr8333 said:
so with this method you dont have to use the motofastboot?
Click to expand...
Click to collapse
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Gus Ghanem said:
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Click to expand...
Click to collapse
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
fakieskr8333 said:
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
Click to expand...
Click to collapse
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Gus Ghanem said:
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Click to expand...
Click to collapse
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
fakieskr8333 said:
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
Click to expand...
Click to collapse
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Gus Ghanem said:
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Click to expand...
Click to collapse
Thanks, I am at work now but as soon as I get home I will give it a go. I have been on iOS for over a year now and my moto has been dead since about a month after moto allowed us to unlock the verizon variant. Stupid thing lol.
how do I check the amount of sparsechunks that I have. Sorry for the dumb question
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
I just finished doing this. I am kind of a noob at this so bear with me. I tried this and I get this message that says "Boot up failed" when I try normal powerup. I'm kind of scared..
ABSOLUTE LEGEND
i was stuck since almost 36 hours, good i dint lose hope and smash the x against the wall
YOUR A LIFE SAVER Fakieskr
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Slupvee said:
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Click to expand...
Click to collapse
It's always a good idea to put your phone in bootloader mode and do:
fastboot getvar all
So you get all the specs of your phone, and copy the info into a Notepad file.
Did you try reflashing TWRP (twrp-3.0.2-1-victara.img)?
If that's not working, you may be able to reflash stock firmware.
https://firmware.center:8081/firmware/Motorola/
Something like this:
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
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Slupvee said:
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Click to expand...
Click to collapse
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Gus Ghanem said:
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Click to expand...
Click to collapse
Verizon moto x 2014 5.1
Hey did u fixed it?
Hello
I can't enable this option for lock bootloader
I tried write fastboot oem lock but I forgot enable this
I flashed NPS26.116-61 and NPSS26.116-45-5 and same
How I can relock my bootloader?
PS : when I flash stock rom in boot and recovery files I have: (bootloader) Image signed with key bad key
Developer options
Adi5 said:
Hello
I can't enable this option for lock bootloader
I tried write fastboot oem lock but I forgot enable this
I flashed NPS26.116-61 and NPSS26.116-45-5 and same
How I can relock my bootloader?
PS : when I flash stock rom in boot and recovery files I have: (bootloader) Image signed with key bad key
Click to expand...
Click to collapse
Expecting u have done everything right and know the basics .And this one worked for me with dec updated firmware. Copy all command cntr+V
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
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 oem lock
fastboot oem lock
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 system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
Kakshay0981 said:
Hoping u have done everything right and know the basics .... And this one worked for me with dec updated firmware. Copy all command cntr+V
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
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 oem lock
fastboot oem lock
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 system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
Thanks
I will try it later
I hope it help and I finally I 'll lock bootloader
And I have last question
It will relock with disabled oem unlocking option? When I tried fastboot oem lock command "cheak oem options"
Adi5 said:
Thanks
I will try it later
I hope it help and I finally I 'll lock bootloader
And I have last question
It will relock with disabled oem unlocking option? When I tried fastboot oem lock command "cheak oem options"
Click to expand...
Click to collapse
I am not sure weather it will work disabled oem.
I read somewhere that to lock we have to enable it so when i was flashing i enabled it.
Kakshay0981 said:
I am not sure weather it will work disabled oem.
I read somewhere that to lock we have to enable it so when i was flashing i enabled it.
Click to expand...
Click to collapse
I enabled it
Solution: flash twrp And root via magisk And I can enabled/disable oem unlock
(bootloader) Still require signed boot.img
OKAY [ -0.000s]
finished. total time: -0.000s
no working
Edit my bad
Thanks,working as charm
thanks! working for me!
It works finally. Thank you man it was helpful
Adi5 said:
Thanks,working as charm
Click to expand...
Click to collapse
What is your model number? XT1804?
Excuse me, but why people want to lock bootloader back? Except ofc to sell it or try to get a warranty service repair.
susemano said:
What is your model number? XT1804?
Click to expand...
Click to collapse
XT1805
osemoka said:
Excuse me, but why people want to lock bootloader back? Except ofc to sell it or try to get a warranty service repair.
Click to expand...
Click to collapse
Pass safetynet without magisk on stock rom(get ota updates)
But I locked bootloader and unlocked them after 1 week?
Adi5 said:
Thanks
I will try it later
I hope it help and I finally I 'll lock bootloader
And I have last question
It will relock with disabled oem unlocking option? When I tried fastboot oem lock command "cheak oem options"
Click to expand...
Click to collapse
Does this work with the moto G5s plus 8t1806 variant and if so what do I flash to relock my bootloader
Dunken415 said:
Does this work with the moto G5s plus 8t1806 variant and if so what do I flash to relock my bootloader
Click to expand...
Click to collapse
Should work
What software version u have now?
Adi5 said:
Should work
What software version u have now?
Click to expand...
Click to collapse
Android version is 7.1.1, and if you want to know the build number it is NPSS26 . 116-45-9
http://pdl.team-eureka.com/other/dd...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash this with commands in this thread
I´m still trying to lock my bootloader, but when I start the phone it shows me the bad key screen and says that it´s till unlock. HEEELP
So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?
Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.
mroneeyedboh said:
So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?
Click to expand...
Click to collapse
spyda256 said:
Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.
Click to expand...
Click to collapse
I have the Unlocked Z3, as well as the Sprint model, and have flashed between stock/CFW many tines. You simply need to use a flash all bat, paired with the stock firmware (current or newer).
However, please keep in mind that the verity message will remain during boot. Locking the bootloader will NOT fix this. If either of you need the bat file lmk.
Edit:
1. Enter fastboot/booloader on phone. Place bat file in SAME folder as unzipped firmware. Android SDK or adb tools must be installed!
2. Try USB2.0 port before 3+
3. Once done, use keys and switch to recovery mode
4. Perform a format
5. Reboot
https://drive.google.com/folderview?id=15hFa95l6bV1idoRXe5L1gt36jpG9s9DG
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 flash bluetooth BTFM.bin
fastboot flash dsp dspso.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_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
pause
First im trying to reinstall stock firmware on a model XT1925-3, from a friend.
It was stuck at Moto Logo, i tried everything you could imagine to make it work. Nothing happens. The things I tried:
-It have locked bootloader (i cant unlock because i cant boot to "Allow OEM").
-Tried all 8 RETBR firmwares (https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/) and none worked.
-Trying the following commands:
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 flash recovery recovery.img
fastboot flash dsp adspso.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 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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
It goes very well, but after restart, it backs to fastboot screen and cant boot.
-Tried another cable, tried another PC, tried another port
-Attached the screen it is now
If theres anything you can do to help me. I appreciated
There's nothing wrong with your cable, your PC or something else! Otherwise you can't even process the first the command in fastboot.
So first thing I would do is booting into recovery. Although it's the stock one it will be very useful to get detailed information in your case.
Once in fastboot mode use the Vol -/+ keys to navigate to reboot to recovery and press power. Then have a look at the logs provided by the recovery. There should be two different kinds of logs - the kernel log and the recovery.log. Choose kernel.log (maybe it's called last_dmsg.log or sth like that). It provides the most detailed information on Android and why you're stuck in a bootloop. Be aware that it has more than one page which will be shown up. Have a look at the left corner on the bottom. Don't expect to find the major error on the last lines, but somewhere in the last 150 lines.
That's one thing you can do.
Another advise is to give the repair tool a chance which is mentioned in your screenshot. This is a really good option in your case.
Good luck!!