Hello,
Sorry if I am asking a dumb question.
My Moto Z is still running Nougat. Both phone and Lenovo Moto Smart Assistant say I have the latest version
I have found many threads about how to flash the Android 8 on this device but actually I am confused because:
My software channel is "retcn" not "retus"
I don't know which guide to follow
So I appreciate if you please help me to find the latest thread about this.
Thank you very much.
Here is your update:
https://mirrors.lolinet.com/firmware/moto/griffin_retcn/official/RETCN
Thank you very much.
Now I don't know which one to download, and should I upgrade to 7.1.1 first (as some guides suggest) or go straight to 8.0.0.
Any help will be much appreciated.
Thanks.
Omid
Shojaei said:
Thank you very much.
Now I don't know which one to download, and should I upgrade to 7.1.1 first (as some guides suggest) or go straight to 8.0.0.
Any help will be much appreciated.
Thanks.
Omid
Click to expand...
Click to collapse
Those are full firmware files, you can flash the newest version
As long as you don't downgrade, and flash the correct software channel it should be fine.
I've posted some instructions here
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Also some instructions here
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712
Sent from my mata using XDA Labs
Hello,
Thank you so much @sd_shadow.
I downloaded the firmware and installed it according to your guide. Now I have two issues:
1) The annoying "your bootloader is unlocked" message after every restart.
2) Bluetooth is not working at all and the SIM card keeps un-registering and I have to restart the phone.
So would you please help me to:
1) Downgrade to 7.0.0 (my device is XT1650-05)
2) Lock the bootloader again to get rid of that warning message.
Thank you very much.
Shojaei said:
Hello,
Thank you so much @sd_shadow.
I downloaded the firmware and installed it according to your guide. Now I have two issues:
1) The annoying "your bootloader is unlocked" message after every restart.
2) Bluetooth is not working at all and the SIM card keeps un-registering and I have to restart the phone.
So would you please help me to:
1) Downgrade to 7.0.0 (my device is XT1650-05)
2) Lock the bootloader again to get rid of that warning message.
Thank you very much.
Click to expand...
Click to collapse
You didn't say anything about the bootloader being unlocked before.
Sent from my mata using XDA Labs
---------- Post added at 08:31 PM ---------- Previous post was at 08:23 PM ----------
If things aren't working, you may have missed a flash command.
Sent from my mata using XDA Labs
@sd_shadow
Sorry for neglecting to mention that. I somehow taught that's obvious.
I have flashed the phone 3 times but bluetooth and sim card issue are not solved.
I appreciate your help to flash back to original 7.0.0 and then lock the bootloader (or lock the bootloader and then flash to 8.0.0 if that's the correct way).
@sd_shadow
Sorry for neglecting to mention that. I somehow taught that's obvious.
I have flashed the phone 3 times but bluetooth and sim card issue are not solved.
I appreciate your help to flash back to original 7.0.0 and then lock the bootloader (or lock the bootloader and then flash to 8.0.0 if that's the correct way).
Shojaei said:
@sd_shadow
Sorry for neglecting to mention that. I somehow taught that's obvious.
I have flashed the phone 3 times but bluetooth and sim card issue are not solved.
I appreciate your help to flash back to original 7.0.0 and then lock the bootloader (or lock the bootloader and then flash to 8.0.0 if that's the correct way).
Click to expand...
Click to collapse
Sounds more like you didn't use the correct commands
Downgrading isn't going to help.
---------- Post added at 04:00 PM ---------- Previous post was at 03:43 PM ----------
Do not lock the bootloader till it's working correctly.
If you downgrade do not install OTA updates.
Sent from my mata using XDA Labs
---------- Post added at 04:13 PM ---------- Previous post was at 04:00 PM ----------
How many system.img_sparsechunk s are in the firmware folder?
Looks like there should be about 14
If the is more or less you need to edit the following commands.
Also run them one at a time, so it's easier to see
If there are errors.
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 dsp adspso.bin
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Sent from my mata using XDA Labs
@sd_shadow
Thank you very much. Would you please share the link to the firmware file again? My device is XT1650-05 (Retail China Dual Sim). I think its codename is Sheridan but all firmwares I find online are named "Griffin". Maybe these two are the same but I need someone to confirm it.
@sd_shadow
Thank you very much. Would you please share the link to the firmware file again? My device is XT1650-05 (Retail China Dual Sim). I think its codename is Sheridan but all firmwares I find online are named "Griffin". Maybe these two are the same but I need someone to confirm it.
Shojaei said:
@sd_shadow
Thank you very much. Would you please share the link to the firmware file again? My device is XT1650-05 (Retail China Dual Sim). I think its codename is Sheridan but all firmwares I find online are named "Griffin". Maybe these two are the same but I need someone to confirm it.
Click to expand...
Click to collapse
Edit: I cannot find any links for Sheridan firmware
https://mirrors.lolinet.com/firmware/moto/griffin_retcn/official/RETCN/
Sent from my perry_f using XDA Labs
@sd_shadow
I downloaded "XT1650-05_GRIFFIN_RETCN_8.0.0_OCC27.102-23_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" from the link you provided and here is the result of third command:
Code:
C:\adb>fastboot flash partition gpt.bin
(bootloader) has-slot:partition: not found
(bootloader) is-logical:partition: not found
Sending 'partition' (142 KB) OKAY [ 0.049s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Please assist.
Shojaei said:
@sd_shadow
I downloaded "XT1650-05_GRIFFIN_RETCN_8.0.0_OCC27.102-23_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" from the link you provided and here is the result of third command:
Please assist.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Copy the results, remove the IMEI if you want, and post it here so we can see if we can figure out something.
Sent from my mata using XDA Labs
@sd_shadow
here you are:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223JRXHF
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 0290F52500000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 09-27-2016
(bootloader) sku: XT1650-05
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 10 8:15: 8 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: 27.76-51/58:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.58.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29R SCD
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g72b40d5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Feb 26 05:47:32 CST 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.02-0-g722a114
(bootloader) tz.git: git=b5f954a-dirty
(bootloader) hyp.git: git=b5f954a-dirty
(bootloader) devcfg.git: git=b5f954a-dirty
(bootloader) keymaster.git: git=b5f954a-dirty
(bootloader) cmnlib.git: git=b5f954a-dirty
(bootloader) cmnlib64.git: git=b5f954a-dirty
(bootloader) prov.git: git=b5f954a-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcn
all: listed above
Finished. Total time: 0.121s
Shojaei said:
@sd_shadow
here you are:
Click to expand...
Click to collapse
I cannot find any links for Sheridan firmware.
Sent from my mata using XDA Labs
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
Unlikely to work
But you could try
Moto smart assistant's
Recovery option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my mata using XDA Labs
Related
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
this files?
eLaDiio said:
this files?
Click to expand...
Click to collapse
I've never noticed them. Actually I've never checked in the ota packages, so thanks maybe those files can help me even if normally there should be only one gpt main 0.bin, so i don't know how can i merge them and if it's possible
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
The Marionette said:
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
Click to expand...
Click to collapse
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
MasterJack1697 said:
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
Click to expand...
Click to collapse
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
The Marionette said:
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
Click to expand...
Click to collapse
Can you please give me te link to this blank flash? I can't find the oreo based one
MasterJack1697 said:
Can you please give me te link to this blank flash? I can't find the oreo based one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
i'll try as soon as possible thanks
eLaDiio said:
this files?
Click to expand...
Click to collapse
anyway those file are totally useless to me, or at least i don't know how to merge them in one file so i can't use them
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
MasterJack1697 said:
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
Click to expand...
Click to collapse
Yeah, you're welcome.
Issue with partition table
Thanks for the blankflash, it did work on Moto Z. I was able to get my phone back to recovery mode.
But now i get the below message when i run "fastboot flash partition gpt.bin"
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
If i try to run other commands, below is the error:
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.281s
Please see if you can help me to overcome these errors.
Thanks.
MasterJack1697 said:
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
Click to expand...
Click to collapse
bmskartik said:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Please see if you can help me to overcome these errors.
Thanks.
Click to expand...
Click to collapse
Did you try deducing the output? I think I even mentioned this.
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
C:\Downloads\XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsi
dy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.09(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 5552ed0g
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E778AC6200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.09-0-g7de07a7
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.140s
The Marionette said:
Did you try deducing the output? I think I even mentioned this.
Click to expand...
Click to collapse
bmskartik said:
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
Click to expand...
Click to collapse
https://www.merriam-webster.com/dictionary/deduce
You are trying to flash an older bootloader over your current one.
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The Marionette said:
You are trying to flash an older bootloader over your current one.
Click to expand...
Click to collapse
bmskartik said:
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
One page backwards, I put a link to my post, where I explained everything I did. The OTA or the whole update zip should have the newest bootloader.
Again, I mentioned everything I did there.
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
bmskartik said:
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
Click to expand...
Click to collapse
Mine did the same, now try flashing the gpt.bin from the whole Oreo firmware, not the OTA.
Sorry for my broken English,
Hey guys i just unlocked the boot-loader to install android 9.0 in it to just enjoy android PIE
and another day i didn't find that custom ROM stable so i flashed the android 7.0 nougat Rom in it through a video a guy posted(how to go back to stock Rom)
Stock Rom name - XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (this is the Rom that i had flashed)
and after that an OTA update just arrived and i quickly started downloading it and after it was going to update through restating the phone it just got hard bricked
i searched the whole day then got a fix through QCOM blank-flash file okayyy then went back to boot-loader,
and after this i have tried every moto g5 plus rom out there but none of it works
i have even tried to flashed the latest firmware
Name - XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
but still the boot-loader says security version downgrade,
.
.
This is exactly what it says :
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.501s
.
i have tried to boot into recovery through TWRP and the Stock and had done everything but it loops in this
{ Your device has been unlocked and cant be trusted.
to learn more , visit motorola bla bla bla
ID: bad key
Your device will boot in 5 seconds. }
.
.
.
.
This is the fastboot getvar all about bootloader
-
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2243GTRP
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 00409F3400000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351892082852554
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 13 20: 0: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.14.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband[0]: M8953_8000.128.06.42u POTTER_INDIADSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g708ac5e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: hu Jan 12 12:24:19 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
.
.
.
please guys every help is appreciated
thank you in advanceeeee
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
outis151 said:
Use this tool here: https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
It is old but it does the job for unbricking your phone. (Have tried it on my device)
Click to expand...
Click to collapse
thank you but still nothing is working
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
devhere_ said:
thank you but still nothing is working
Click to expand...
Click to collapse
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
Sent from my Moto G5 Plus using XDA Labs
outis151 said:
After reading your post again i see that you are getting "Security version downgrade" errors. This is because you can not downgrade a bootloader.
But if you use the tool i showed you and flash the boot_image from there and then the stock Rom it should be fixed...
Is that what you tried?
Click to expand...
Click to collapse
yes exactly this way but no luck still looping in bootloader
Wolfcity said:
@outis151 is right, all you have to do is flash a new (new means in this case newer than the one you were on before you changed to a custom ROM).
I don't like tools so I would prefer to fastboot flash the latest available signed Motorola firmware which is 28.85.17.6.2:
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
I'm not sure if this is the correct one for your region but that doesn't matter, there won't be any further OTA updates in the future and the firmware is running on every Moto G5+, you just don't get any OTA updates anymore.
So take this flashall.bat :
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
(or write the commands by hand) and flash this firmware on your device (attention, your data will be lost).
This should make your device work again.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
devhere_ said:
okay sir i have done the same way you told me to do but the same process is happening with this rom also
what should i do next?
Click to expand...
Click to collapse
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Directly after flashing that firmware take a recovery.log in TWRP and attach it here. You can grab it with TWRP terminal.You'll find the log in the root directory under cache/recovery/last_log.
To attach it here change the ending from log to txt or upload it to some kind of hoster or pastebin.
Most probably the OTA has downgraded your bootloader which could have caused a hard brick.
Have you tried to flash a custom ROM?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
i cannot even boot into my recovery not stock nor TWRP
how can i attach that recovery.log here ??? if i could boot into twrp i"ll flash a custom rom but unfortunately i cannot boot into recovery
all i can do things is my boot-loader nothing else is working
Hello everybody!
My brother got a Moto One (XT 1941-3) last year and tried to flash it, but somehow he got the wrong Rom and bricked it.
I'm trying to recover the phone to its stock rom, but the device says that it is OEM_locked, so I can't install a new firmware on it.
fastboot oem unlock asks for a code (which is given when you input the unlock data in moto support website) , but fastboot oem get_unlock_data displays that "unlock data unavailable"
fastboot getvar all is here:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-6f8d34a-190722
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0050511872
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: B8C94CFA00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: 359547090224541
(bootloader) meid:
(bootloader) date: 01-10-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 27 14:28:52 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-11/b3804:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.381.12.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_16.15.02.23R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-gb0f0dde (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Jul 22 06:12:31 CDT 2019
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-6f8d34a-190722
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.103s
{
"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"
}
Any possible solutions?
Karlloz said:
Hello everybody!
My brother got a Moto One (XT 1941-3) last year and tried to flash it, but somehow he got the wrong Rom and bricked it.
I'm trying to recover the phone to its stock rom, but the device says that it is OEM_locked, so I can't install a new firmware on it.
fastboot oem unlock asks for a code (which is given when you input the unlock data in moto support website) , but fastboot oem get_unlock_data displays that "unlock data unavailable"
fastboot getvar all is here:
Any possible solutions?
Click to expand...
Click to collapse
Did you try to flash stock boot.img anyway? Maybe because it has a wrong rom it displays wrong info.
borksek said:
Did you try to flash stock boot.img anyway? Maybe because it has a wrong rom it displays wrong info.
Click to expand...
Click to collapse
Tried it again now:
Code:
fastboot flash boot boot.img
error: Failed to identify current slot
Then I tried to boot it directly:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.813s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.824s
Setting a or b slots to active also doesn't work:
Code:
fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
Semms that it needs to unlock the bootloader, but, as my first post explain, I'm unable to unlock it :crying:
Karlloz said:
Tried it again now:
Code:
fastboot flash boot boot.img
error: Failed to identify current slot
Then I tried to boot it directly:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.813s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.824s
Setting a or b slots to active also doesn't work:
Code:
fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.019s
Semms that it needs to unlock the bootloader, but, as my first post explain, I'm unable to unlock it :crying:
Click to expand...
Click to collapse
I see in getvar that cid returns 0x0000.which means it's unlockable. You probably wouldn't be able to unlock it anyway since you first have to enable the "oem unlock toggle" in dev settings before you can get it unlocked in fastboot.
Question is how he was able to flash it in the first place if it's locked, unless it's possible to flash original files without unlocking.
Have you tried to full flash latest retbr firmware or tried to use lenovo/moto smart assistant to recover it?
tys0n said:
I see in getvar that cid returns 0x0000.which means it's unlockable. You probably wouldn't be able to unlock it anyway since you first have to enable the "oem unlock toggle" in dev settings before you can get it unlocked in fastboot.
Question is how he was able to flash it in the first place if it's locked, unless it's possible to flash original files without unlocking.
Have you tried to full flash latest retbr firmware or tried to use lenovo/moto smart assistant to recover it?
Click to expand...
Click to collapse
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Karlloz said:
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Click to expand...
Click to collapse
Try doing flash bootimage boot_a
borksek said:
Try doing flash bootimage boot_a
Click to expand...
Click to collapse
Tried a couple commands related to boot.img:
Code:
fastboot flash bootimage boot_a
error: cannot load 'boot_a': No such file or directory
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
Code:
fastboot flash boot_a boot.img
target reported max download size of 534773760 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.018s]
writing 'boot_a'...
OKAY [ 0.911s]
finished. total time: 2.932s
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.805s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.813s
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Karlloz said:
Tried a couple commands related to boot.img:
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Click to expand...
Click to collapse
Im not really good with Motorola's but with Samsung's atleast, you should be able to flash stock without any problem, as long as it's signed
Karlloz said:
Maybe the phone was unlocked during the flashing of the wrong ROM, but after it locked itself? Dunno, really doesn't make sense...
I tried to flash all the the stock rom, and to use the assitant, but none could solve the problem.. when flashing using the commands from 'flashfile.xml' (converted to .bat), all files output "okay", but after rebooting it stills goes back to the same "no bootable a/b slot".
Click to expand...
Click to collapse
I guess I was wrong about cid 0x0000. They can be unlocked, but for that to happen you'd have to first enable oem toggle in developer settings, then get the unlock data in fastboot mode, send the data to motorola which will then send the unlock key to you. Any idea if he's done that?
And no, it shouldn't lock itself without proper lock commands in fastboot mode.
So your flash commands looks like this?
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
same problem
I have the same problem, did you find a solution?
contacto
ISRAELSANDOVAL29292 said:
I have the same problem, did you find a solution?
Click to expand...
Click to collapse
hablas español hacemos contacto x whatss
---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------
Karlloz said:
Tried a couple commands related to boot.img:
Code:
fastboot flash bootimage boot_a
error: cannot load 'boot_a': No such file or directory
Fastboot seems to be searching for boot_a as a file, not as the partition. Then I tried to invert the command:
Code:
fastboot flash boot_a boot.img
target reported max download size of 534773760 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.018s]
writing 'boot_a'...
OKAY [ 0.911s]
finished. total time: 2.932s
it did transfer the file to boot_a, but when I rebooted the phone to check, still got the same error, no change. Tried to flash into boot_b too, exaclty the same...
Also:
Code:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.805s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 1.813s
There should be some way to unlock the bootloader, it appears to be the only reason i cant flash the system..
Click to expand...
Click to collapse
hi are you flashing with fastboot commands or are you using some software. use RSD lite
alguien encontró solucion tengo el mismo problema
lucasymax said:
hablas español hacemos contacto x whatss
---------- Post added at 09:22 PM ---------- Previous post was at 09:13 PM ----------
hi are you flashing with fastboot commands or are you using some software. use RSD lite
Click to expand...
Click to collapse
Hi there! just for rules, I wrote in english, but I speak spanish, anyway I have same trouble, pm to create wsp group.
reply
darwyn001 said:
Hi there! just for rules, I wrote in english, but I speak spanish, anyway I have same trouble, pm to create wsp group.
Click to expand...
Click to collapse
hey bro, have you managed to solved that?
Dahirock said:
hey bro, have you managed to solved that?
Click to expand...
Click to collapse
Not yet! I tried flashing every security patch downloaded from Lolinet, nothing fix it.... I will wait for Q and try again
tengo el mismo problema
alguien pudo encontrar una solucion motorola one 1941-3
I've tried with android Q and and still have the same result
darwyn001 said:
Not yet! I tried flashing every security patch downloaded from Lolinet, nothing fix it.... I will wait for Q and try again
Click to expand...
Click to collapse
I've tried flashing XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC rom via fastboot and RSDlite and sill have the same problem
J4m3sB4rn3s said:
I've tried flashing XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC rom via fastboot and RSDlite and sill have the same problem
Click to expand...
Click to collapse
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
sd_shadow said:
Try LMSA's Flashing/Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
That was my first attempt to unbrick my phone, but didn't work
J4m3sB4rn3s said:
That was my first attempt to unbrick my phone, but didn't work
Click to expand...
Click to collapse
I think your device is bricked same as mine. I have been flashing every phone that I have owned and never have I bricked a phone but even with that experience i understand that mine was a novice mistake flashing a lower version of Android. I think you will need to look at qcom blank-flash options.
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
coltswalker said:
This Moto G Power is currently running QPMS30.80-63-6-8-3 and therefore I downloaded XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, patched the boot.img with Magisk and wrote to the phone with fastboot.
Phone on reboot has no touch screen control and erroneously indicates no battery charge. Appears to be a symptom of mismatch of boot.img from downloaded firmware and what is actually on the phone. I don't know how as I downloaded the same version. Obtained firmware from Lolinet. It is a carrier unlocked phone.
Suggestions to other ops in other posts refer to Lenovo's Rescue and Smart Assistant (LRSA) however I have no Microsoft Windows machines in my environment. I have access to Mac and Linux.
Im not sure why the firmware was a mismatch. My phone clearly indicates it is model model XT2041-4 and QPMS30.80-63-6-8-3 which should be a match for what I downloaded. Undocumented variants?
How can I recover this phone using a Linux machine since LRSA is not an option? What are my options? It was my intention to simply root patch to boot.img with magisk (Ive done before with other phones) and apply with fastboot.
What I have tried thus far: booting with unpatched boot.img .. fail and downloading firmware from another source, writing boot.img .. fail.
moto g power
model XT2041-4
software: US Retail
Android 10
QPMS30.80-63-6-8-3
Phone did not come as QPMS30.80-63-6-8-3 it was OTA updated to QPMS30.80-63-6-8-3.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
coltswalker said:
```
(bootloader) version-bootloader: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) date: 11-03-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-63-6-8-3/3a94d:user/release
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Oct 8 14:0
(bootloader) kernel.version[3]: 2:49 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-37f1d8316-201101
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-201101
(bootloader) git:tz: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:hyp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:devcfg: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:keymaster: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) gitrov: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) git:abl: MBM-3.0-sofia_retail-20deb5d119-201101
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-201101
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-5ea560fb-201101
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
```
Click to expand...
Click to collapse
Looks ok to me.
Maybe the boot.img you downloaded is corrupt.
Did the .zip look like right size?
I guess I would download the next newest firmware and try to flash that boot.img
If that works flash the rest.
I have some Windows instructions Linux should be the same.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version. Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
On another note: In all of the research I have done online with this model there are some sites that confuse sofia and sofiar as I have seen firmware for G advising sofiar which is clearly wrong. I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8. As I understand the model XT2041-4 is the G however some other sources online have it the other way. It is unfortunate that Motorola / Lenovo made the distinction of models of such similar hardware so confusing.
coltswalker said:
I am confused by reading your response. By "next newest" you mean to go backwards to the previous firmware version?
Click to expand...
Click to collapse
Yes
You say "flash boot.img if that works then" so you mean to flash an older boot.img from the previous firmware onto
Click to expand...
Click to collapse
yes
the phone which is running a newer firmware? That seems like a bad idea since the boot.img from a previous firmware would not be of the same version.
Click to expand...
Click to collapse
I meant if it flashes without error, not fit boots.
Finally it looks like you advise to flash the entire firmware if the phone is
able to boot with the boot.img from previous.
Id like to clarify before proceeding.
Click to expand...
Click to collapse
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
I hope that lolinet is offering the true sofia firmware and not that for sofiar G8 as I have a G not G8.
Click to expand...
Click to collapse
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
sd_shadow said:
You posted
Code:
writing boot.img .. fail.
If you could flash the older boot.img maybe flashing older firmware will get the phone booting again.
You also could compare the older boot.img size with the newer.
Unlikely they got it wrong
see
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
Click to expand...
Click to collapse
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
coltswalker said:
I am sorry I think I failed to articulate that well enough. The flash process itself did not fail. I have had no trouble writing to the phone from the computer in any event. What failed was seeking a solution to the problem of the phone not responding to touch screen activity. Every time I have used "fastboot" to write to the phone the write process itself completed successfully.
So, what I wanted to test on that occasion was if Magisk corrupted the boot.img so I flashed the unpatched boot.img, which also resulted in the same problem of the phone not responding to touch screen activity. This way I eliminated Magisk as the culprit and decided that the firmware I got from lolinet was not an exact match for my phone or firmware version.
Also, I have read "all about official firmware and where to find it" and I note some issues with that document. Firstly, it is very Microsoft Windows tool centric. Secondly, it fails to recognize that there are two models of the Moto G like mine for US market, one having more memory to better match the G8, although it is still a Moto G.
If the firmware from lolinet was an exact match, I would not be in this sticky situation as of right now the phone is rather useless to me. I have no idea how to obtain a boot.img that matches the phone firmware since the one from loli and one from another place neither worked thus far.
Click to expand...
Click to collapse
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
justinr34gtr said:
I was having issues reverting to stock boot.img earlier today. I had forgot that it needed to be flashed with fastbootd instead of fastboot. As far as I know, the only way to get into fastbootd is from the stock recovery.
Click to expand...
Click to collapse
Code:
fastboot reboot fastboot
Hi all,
I am a newbie to custom ROM's world and this is my attempt to it. My device is Moto G5s Plus.
To start with I had an encrypted phone running Android 8. Encryption was mandatory to install some work related apps. Because of sluggish performance I thought to install custom ROM.
Here are the steps I followed:
1. Installed minimal ADB on my laptop running Win10. Connected phone and successfully unlocked bootloader.
2. Rebooted phone in recovery mode and installed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'.
3. Rebooted the device and everything was working fine till now (restored from google backup and restarted several times to make sure things were working fine).
4. Now as I mentioned I need to encrypt phone for bussiness reasons. So I selected 'Settings->Encrypt Phone'. For very small time a green iconed screen appeared and then phone rebooted.
5. After reboot, a screen with google logo (G) with a small progress bar (kept moving left to right and vice-versa) appeared. I left it for more than 12 hours still hung at same screen.
6. Now I tried to wipe Dalvik/ART cache and cache. This is where problem started happening. I tried few other things (could not recollect exactly). I even tried to erase 'data' from fastboot using 'fastboot erase userdata'.
7. When nothing worked, I thought of installing Pixel Experience 11 plus again from TWRP. The process went smooth but towards the end it showed:
'Failed to mount '/data' (invalid argument)' error.
I am attaching snapshots and logs. Its been more than 3 days being stuck on this issue. Really appreciate any help.
Please let me know if any info is required.
Also since I dont have any data to worry about, so I am open to any suggestion (wipe/format). I have SD card and OTG with me.
Once the phone is up and running, I need to encrypt it back. So please suggest steps while keeping this requirement in mind.
Look for this issue on youtube and you'll find the steps to fix it.
It looks like you have a corrupt file system.
You can fix it using TWRP.
Good luck !
Hi,
I tried multiple steps to fix this issue but none helped.
As for now looks like I have made some progress. What I did was i flashed official firmware for Moto G5s plus as mentioned on below page:
Flash official firmware Moto G5s Plus [sanders]
So far, we have had the guides for you to unlock the bootloader in Moto G5s Plus or how to install TWRP on Moto G5s Plus and today, I am going to show you how to download and Install stock ROM in Moto G5s Plus. So if you probably have already...
forum.xda-developers.com
With this I got the device up and running with Android 7. Below is the full log of fastboot getvar all command:
<<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all > and7_var
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 4:57:41 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-4/4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.201.4.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g419eefd0-000
(bootloader) kernel.version[1]: 54-g1b4a83e ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Mon Oct 16 22:03:44 CDT 2
(bootloader) kernel.version[4]: 017
(bootloader) sbl1.git: git=MBM-NG-VC2.06-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) devcfg.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) keymaster.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib64.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) prov.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.121s
>>>
Now i have Android 7 up and running. Now I opened TWRP again, and flashed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'. Though this process works fine but after reboot it is again stuck at Google logo (G) screen.
Please help. I have spent 2-3 days working this out.
Regards.
Hey man.
In order to flash PE 11, like the ROM topic says, you "MUST" be on latest modem baseband ...
You "ONLY" obtain that by flashing the latest OREO 8.1 ROM.
So, you should flash latest Oreo you have and update it till there are no more updates.
Read PE 11 topic again. There you can find out about what i'm saying here.
Hope this helps and again,
Good luck !
Thanks a lot Damage1972 for showing the way forward
Between how did you figured out if this is the issue here?
Based on your suggestion, I flashed stock Android v8.1 and updated it till there are no updates. Phone was rebooting fine. After this, I flashed PE 11 plus and again phone is stuck at Google logo (G) screen.
Between below are logs:
<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 9:30:53 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.065s
>>
Please suggest.
Thanks and Regards.
No problem,man.
About the issue, it's listed on the pre requests in order to flash PE 11 !
It's very clear written on the first page and comments on the topic.
Carefully read the ROM's topic before flashing...
About your phone still stuck on boot : did you go through the steps to correct your phone file system ? And (sorry to ask you this) how did you flash the ROM ?
Did you do a Clean Flash ?
Check your messages.
Also, try this , that's what worked for me :
How to fix unable to mount data internal storage 0mb in twrp permanently :
Note : This will wipe/format your Data partion and your data will be reset. INSTRUCTIONS : 1) Reboot your device into TWRP Recovery. 2) Go to Wipe menu. 3) Go to Advance Wipe. 4) Select Data and go to Repair or Change File System. 5) Click...
forum.xda-developers.com
So few updates:
1. Looks like my mount data internal storage 0 mb issue is resolved (flashed stock ROM and then custom ROM and did not see this error).
2. Regarding how I flashed stock ROM Android 8.1. I downloaded 'Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0.zip' image from:
Motorola Moto G5S Plus XT1804 Stock ROM Firmware (Flash File)
Download the official Motorola Moto G5S Plus XT1804 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
and executed below commands in order:
<<
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition sanders81/gpt.bin
fastboot flash bootloader sanders81/bootloader.img
fastboot flash modem sanders81/NON-HLOS.bin
fastboot flash fsg sanders81/fsg.mbn
fastboot flash dsp sanders81/adspso.bin
fastboot flash logo sanders81/logo.bin
fastboot flash boot sanders81/boot.img
fastboot flash recovery sanders81/recovery.img
fastboot flash system sanders81/system.img_sparsechunk.0
fastboot flash system sanders81/system.img_sparsechunk.1
fastboot flash system sanders81/system.img_sparsechunk.2
fastboot flash system sanders81/system.img_sparsechunk.3
fastboot flash system sanders81/system.img_sparsechunk.4
fastboot flash system sanders81/system.img_sparsechunk.5
fastboot flash system sanders81/system.img_sparsechunk.6
fastboot flash system sanders81/system.img_sparsechunk.7
fastboot flash system sanders81/system.img_sparsechunk.8
fastboot flash system sanders81/system.img_sparsechunk.9
fastboot flash system sanders81/system.img_sparsechunk.10
fastboot flash oem sanders81/oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg sanders81/fsg.mbn
fastboot oem fb_mode_clear
fastboot reboot
>>
After that I was able to turn ON phone with Android 8.1.0. Checked for updates and installed them (i guess there were 3 security updates). Once done, entered bootloader and installed TWRP and flashed PE 11 plus. After reboot, it is again stuck at google logo (G) screen.
One more suggestion i need: Since I have spent a lot of time debugging this and ultimately I have to encrypt my phone. So below queries:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
andromeda1410 said:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
Click to expand...
Click to collapse
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Thanks sBinnala for help. At this point I am convinced that I will not install custom ROM. So I want to have stock ROM (Android 8.1) preferably.
Thing is yesterday I installed Android 8.1 stock rom (exact steps mentioned above), worked fine. Flashed PE 11 plus and phone got stuck at google logo screen. Searched again and though it to be some modem related issue hence I did below steps as mentioned on https://forum.xda-developers.com/t/rom-11-sanders-pixelexperience-normal-plus-aosp.4247243/ by Jorge:
<<
It is recommended that you are using the latest firmware for the Moto G (5S) Plus.
to update via twrp:
Modem only:
https://sourceforge.net/projects/ne...5-36-14_v2.0-modem-only_20210307.zip/download
Modem, Fsg & dsp:
https://sourceforge.net/projects/ne...S28.65-36-14_v2.0-modem_20210307.zip/download
>>
So I flashed Modem, Fsg & dsp: (second zip) and re-flashed PE 11 plus. Again that did not worked. Now again I tried to flash stock Android 8.1 ROM. It worked but now it is not detecting SIM., showing IMEI as 0 or not available.
I have found multiple pages on similar issue but none is working. Looks like this issue is because of persist file and epf partition which I dont have (infact i dont have any backup).
So can someone please help me in installing stock Android 8.1 which should work fine (sim should be detected). Any help will be deeply appreciated.
Edit: Tried installing Validus and following steps mentioned on https://forum.xda-developers.com/t/...ork-imei-0-after-flashing-custom-rom.3745474/ but issue not resolved.
If it matters, mine is 4 GB/64 GB, XT 1804 variant.
On some threads, i found inconsistency in architecture (like 32 bit and 64 bit). What is that? I know i have 32 bit TWRP running on a 64 bit Windows 10 machine. I am not sure about stock ROM architecture. Can someone tell me how to check stock ROM architecture?
On another notes: I have tried flashing below stock roms but none of them are working fine (device boots but unable to recognize SIM):
- Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0_Android8.1.zip
- SANDERS_NPSS26.116-26-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_Android7.zip
- SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- Stock-Sanders_OPS28.65-36-14_v2.0-modem_20210307.zip
- Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
Regards.
Further update:
Looks like I have created a backup using TWRP of original ROM (which was Android 8.1 but encrypted). Zipped it using Android app and then I transferred it to Windows laptop (later realized i should not have done it). Unzipped in android device and placed it in OTG. Restored using TWRP but it is not booting.
Can I do anything now? That is, should I preserve any file which I can later use with stock Android 8.1 ROM which can help me with getting sim signal/IMEI number back.
sBinnala said:
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Click to expand...
Click to collapse
Encryption works flawlessly with Arrow 11 vanilla.
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
okayk said:
Encryption works flawlessly with Arrow 11 vanilla.
Click to expand...
Click to collapse
Arrow isn't enforcing - it's permissive, which in itself is a huge security risk. Like I said, we don't have a ROM which supports both SELinux enforcing and encryption at the same time.
andromeda1410 said:
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
Click to expand...
Click to collapse
Normally in such cases, restoring EFS backup will do the trick. Have you already tried that?
After days of investigation, debugging and trying out everything which any post said, I have resolved my issue now. I now have a fully functional Android 8.1 installed on my phone, I am able to make calls, IMEI number is back.
In interest of wider public let me post what worked for me:
Note:
My device is Moto G5S Plus XT1804, 4 GB/64 GB, Retin Channel, India based phone. It is unrooted but has unlocked bootloader.
I have tried a lot many things, flashed many ROMs from different channels but none of them worked.
Below is what worked for me.
Probable issue: During flashing gpt.bin I was getting below error:
<<
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.074s
>>
I guess this is the core issue. I searched on it and got many forums. Finally below solution worked for me:
Downloaded stock Android 8.1 rom 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' for my device from: https://www.stockrom.net/2020/04/xt1804-retin-oreo-ops28-65-36-14.html
Unzipped this file and placed it at 'C:\Program Files (x86)\Minimal ADB and Fastboot'.
Created my own batch file using instructions mentioned in 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/flashfile.xml'.
Imp note: Do not use fastboot commands mentioned on any forum. Every rom (custom/stock) has a flashfile.xml or servicefile.xml. Open this file and create your own batch file with steps in order mentioned in xml file.
Booted my phone in fastboot mode (volume down + power). Connected phone with PC using usb cable.
Launch 'Minimal ADB and Fastboot' on windows PC. Note: i am attaching all tools that i used to rest version related questions.
Run the batch file you created in step #3.
With these steps, I was able to get my phone up and running. Thanks a lot to all members for their help.
Regards.
Reference links:
How to Restore Stock Firmware on Moto G (All Models)
Follow this guide to restore stock firmware on Moto G. The instructions will work for Moto G 1st Gen, 2nd Gen, 3rd Gen, 4th Gen, Moto G5/Moto G5 Plus, and Moto G5S/Moto G5S Plus. The Moto G series is…
www.thecustomdroid.com
G5s Plus XT1804 RETIN (SANDERS) 8 Oreo StockRom OPS28.65-36-14
Download Firmware + Tutorial Completo para Instalação Stock Rom Moto G5s Plus XT1804 (SANDERS) Android 8.1.0 Oreo Loop, Boot Infinito ou Hard Reset
www.stockrom.net
Tutorial – Instalação Stock Rom Motorola no Modo Fastboot (Snapdragon, Moto G, Moto E, Moto X, Moto Z, Moto C, Moto M, One) + Video Tutorial - Stock Rom
Como instalar firmware nos motorolas com processadores snapdragon, moto g1 ao g7, procedimento simples, instalador com 1 clique, sem linhas de comando.
www.stockrom.net
(These pages are in non-english. I used google translator for understanding it)