[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
Moto G5S
2017
XT1793, XT1794 (Europe, India)
XT1795 (India)
XT1792 (Brazil)
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[Index]Motorola Flashing Utilities, Firmware, and more
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
FAQs
UnLocking the Bootloader
ReLocking the Bootloader
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
Firmware
https://mirrors.lolinet.com/firmware/moto
Specs
Hey! I recently got this specific device with 32 GB of internal storage (non plus model) I have about 3 devices of Android modding experience. Is it recommended to unlock it and put a custom ROM on it? Or should I stay stock???
Some random said:
Hey! I recently got this specific device with 32 GB of internal storage (non plus model) I have about 3 devices of Android modding experience. Is it recommended to unlock it and put a custom ROM on it? Or should I stay stock???
Click to expand...
Click to collapse
Whether a custom rom is a good option is really your decision.
In general moto stock rom is more stable and battery efficient,
but Moto often is slow with security patches and new Android versions.
Custom roms offer newer Android versions customizations and features.
If you unlock the bootloader, it may not be easy to relock.
Sent from my mata using XDA Labs
Thank you for the feedback! Guess I will unlock as soon as the first Android 10 ROM is out (or smthn else big)
Hi, I need help. My Moto G5S (XT1794) was on stock ROM but beginning to have issues with apps crashing and even occasionally rebooting randomly. I decided to see if a change of OS would do it some good. I've flashed plenty of phones previously with Cyanogenmod and LineageOS so I'm not exactly a noob but I'm just following the simple steps.
I used this thread to find links to the builds, TWRP and GApps:
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-16-0-t3911496
I unlocked the bootloader, loaded twrp-3.3.1-1-montana.img and then flashed LineageOS 16.0 v0.15. Every time I reboot I get the 'can't be trusted' warning message (which I understand is normal), then the LineageOS boot screen appears for quite a long time cycling, then the phone simply reboots back into TWRP. I've tried using LineageOS 16.0 v0.14 and either flashing GApps or not with the same results. I've even tried twrp-3.3.1-0-montana.img and wiping the caches after each install.
In desperation I tried to flash back to stock ROM from here but the flash fails:
https://mirrors.lolinet.com/firmware/moto/montana/official/RETGB/
I'm out of ideas! Can anyone help?
bifter said:
Hi, I need help. My Moto G5S (XT1794) was on stock ROM but beginning to have issues with apps crashing and even occasionally rebooting randomly. I decided to see if a change of OS would do it some good. I've flashed plenty of phones previously with Cyanogenmod and LineageOS so I'm not exactly a noob but I'm just following the simple steps.
I used this thread to find links to the builds, TWRP and GApps:
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-16-0-t3911496
I unlocked the bootloader, loaded twrp-3.3.1-1-montana.img and then flashed LineageOS 16.0 v0.15. Every time I reboot I get the 'can't be trusted' warning message (which I understand is normal), then the LineageOS boot screen appears for quite a long time cycling, then the phone simply reboots back into TWRP. I've tried using LineageOS 16.0 v0.14 and either flashing GApps or not with the same results. I've even tried twrp-3.3.1-0-montana.img and wiping the caches after each install.
In desperation I tried to flash back to stock ROM from here but the flash fails:
https://mirrors.lolinet.com/firmware/moto/montana/official/RETGB/
I'm out of ideas! Can anyone help?
Click to expand...
Click to collapse
Are you doing the fastboot -w
Before flashing lineage OS!
Sent from my mata using XDA Labs
sd_shadow said:
Are you doing the fastboot -w
Before flashing lineage OS!
Click to expand...
Click to collapse
Tried again, like this?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15850 KB)...
OKAY [ 0.517s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.250s]
finished. total time: 0.797s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.110s]
erasing 'cache'...
OKAY [ 0.000s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
No joy! I proceeded to flash the latest LineageOS and GApps images (with some errors about not being able to mount cache partition, etc) but now the phone is simply rebooting to the bootloader (after 10 minutes on the OS bootscreen). From there I can boot into recovery again.
bifter said:
Tried again, like this?
No joy! I proceeded to flash the latest LineageOS and GApps images (with some errors about not being able to mount cache partition, etc) but now the phone is simply rebooting to the bootloader (after 10 minutes on the OS bootscreen). From there I can boot into recovery again.
Click to expand...
Click to collapse
Don't know
When you flashed stock did you use
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
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
Or something else.
Sent from my mata using XDA Labs
sd_shadow said:
Don't know
When you flashed stock did you use
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
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
Or something else.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Sorry, had to go to bed as I had an early start. I followed a similar procedure but not from an XDA forum and I guess someone got the steps wrong! I found an alternative post on XDA which eventually worked for me. (Flashing the gpt.bin failed the first time round so I left that out and there were 9 sparsechunk files.) I'm now back at stock ROM and it immediately received an OTA security update, now shows:
Android version: 8.1.0
Current version: OPPS28.65-37-7-11
Security patch level: August 1, 2019
It's not clear to me if this is up to date, the Motorola Web site is full of broken links.
The original reason for installing a custom ROM was because the phone was becoming laggy, some apps were crashing and occasionally the phone was rebooting randomly. I think I'll wait and see if this is resolved as I don't fancy going back through that Faustian loop again. Thanks for taking the time to help.
I have the xt1799-2, can i flash the firmware of any of these versions on that phone?
if yes, do i need to flash a rom if i just want to use stock oreo?
Can I just flash the update directly, or do I need to flash to 7.1.1 and then update?
Source Files:
https://mirrors.lolinet .com/firmware/moto/montana/
Thanks so much, I've been trying to figure this out for over 10 hours.
sd_shadow said:
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
Moto G5S
2017
XT1793, XT1794 (Europe, India)
XT1795 (India)
XT1792 (Brazil)
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[Index]Motorola Flashing Utilities, Firmware, and more
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
Click to expand...
Click to collapse
Moto G5s xt1792 HARDEST brick
Hello,
I'd like to know if it's worth getting a micro SD for trying the mmcblk0.img flashing, because for what it sounds, I don't see a way it would work.
Considerations:
Rescue and Smart Assistant (LMSA) tried. First times, it did recognized the device but failed on 80%; after about two tries, it stopped recognizing the device;
All drivers for usb installed;
I can only get commands working through fastboot;
Trying to flash a stock rom through fastboot returns bootloaders errors for every command;
No adb commands work;
Blank Flash doesn't recognized any connected devices.
This is what cmd returns me for "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2e1801a1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: E37B906C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(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) 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: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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
If the info above isn't enough, please, guide me into getting the info you need to help solving this issue, or — at least — giving me the relief of knowing I'm not throwing my money away for buying another phone.
Thank you very much in advance!
phkoon said:
Hello,
I'd like to know if it's worth getting a micro SD for trying the mmcblk0.img flashing, because for what it sounds, I don't see a way it would work.
Considerations:
Rescue and Smart Assistant (LMSA) tried. First times, it did recognized the device but failed on 80%; after about two tries, it stopped recognizing the device;
All drivers for usb installed;
I can only get commands working through fastboot;
Trying to flash a stock rom through fastboot returns bootloaders errors for every command;
No adb commands work;
Blank Flash doesn't recognized any connected devices.
This is what cmd returns me for "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12(*)
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2e1801a1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: E37B906C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(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) 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: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(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
If the info above isn't enough, please, guide me into getting the info you need to help solving this issue, or — at least — giving me the relief of knowing I'm not throwing my money away for buying another phone.
Thank you very much in advance!
Click to expand...
Click to collapse
The device must be in EDL mode to use a blankflash, mmcblk0 or loader.img
Looks like the bootloader is locked, so you cannot force it to EDL mode.
Only fastboot commands work in fastboot mode.
If you have a windows 7 PC try RSD Lite, it doesn't work well with most win 10 machines.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
sd_shadow said:
The device must be in EDL mode to use a blankflash, mmcblk0 or loader.img
Looks like the bootloader is locked, so you cannot force it to EDL mode.
Only fastboot commands work in fastboot mode.
If you have a windows 7 PC try RSD Lite, it doesn't work well with most win 10 machines.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I'll try it out and get back with the results, thanks for your reply.
What is the best ROM for gaming? I could only play on stock 8.1 arm32 and I noticed that the roms that are all arm64 have problems with games, for example crashes and heating above normal.
Related
hi friends my moto g5 xt1677 is stuck in bootloop,able to access fastboot and recovery mode.I don't want to lose my data so is there any way I can get back my data.I have heard that if i update it to the latest security patch or current security patch i may be able to start my phone. I had december security patch installed.If anyone is having december ota file or february ota file please send the link.I am able to boot in recovery mode
recovery mode version below
motorola/cerdric_retail/cedric 8.1.0/OPPS28.85-19-2/73f5
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=07 FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3222CC4J
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc4
(bootloader) uid: 2A7E7F7700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358222070469919
(bootloader) meid:
(bootloader) date: 03-08-2017
(bootloader) sku: XT1677
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 20 6:49:17 UTC 2018"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(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-ga87df5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Dec 20 00:55:53 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3213759-dirty
(bootloader) devcfg.git: git=3213759-dirty
(bootloader) keymaster.git: git=3213759-dirty
(bootloader) cmnlib.git: git=3213759-dirty
(bootloader) cmnlib64.git: git=3213759-dirty
(bootloader) prov.git: git=3213759-dirty
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: amzin
(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.247s
C:\adb>
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
https://mirrors.lolinet.com/firmware/moto/cedric/official/
G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this
Click to expand...
Click to collapse
G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this i dont want to lose my data
Click to expand...
Click to collapse
You could Google flash stock firmware moto g5
I've already provided link to firmware
If your phone bootloops etc you may have no choice but to erase data
Put phone in fastboot mode
Connect phone to PC via USB
Open a terminal/cmd window where you have fastboot files (Google is your friend) and firmware
Type the following in terminal window/cmd
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata (only if you want to erase data or phone bootloops etc)
fastboot oem fb_mode_clear
fastboot reboot
I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?
Mobilettchen said:
I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?
Click to expand...
Click to collapse
Here is the firmware for your device
https://mirrors.lolinet.com/firmware/moto/cedric/official/TEFES/
If you still want to downgrade from oreo to nougat then just don't flash the gpt and bootloader, if you flash the device will hard bricked.
For custom roms you can use carbon ROM.
You need 64 bit twrp to flash.
@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?
Mobilettchen said:
@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?
Click to expand...
Click to collapse
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.
riyan65 said:
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.
Click to expand...
Click to collapse
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone
Mobilettchen said:
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone
Click to expand...
Click to collapse
Oh sorry I forgot to tell that, which ever software channel you flash nothing will happen as the device is not going to receive any more software updates so it does not affect any thing, as for cellular every firmware will work for every country.
Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 3
all: listed above
finished. total time: 0.172s
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot boot twrp-3.2.3-2-nash.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 30.773s
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny
bennyschw said:
Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny
Click to expand...
Click to collapse
Looks like getvar all says Retail
But you are flashing Reteu?
Try
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
Sent from my mata using XDA Labs
Goot moring,
tried to flash this version with the flashall tool, same result.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.222s]
finished. total time: 0.222s
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.302s
Those lines above are the first ones with the flashall tool. Flash permission is always denied so nothing changes.
When I try to boot via fastboot boot boot.img the Motorola Logo appears for 30 secounds and then goes to fastboot again.
The problem is, that flasing is locked and I need to unlock it somehow. But its not possible without some Android system running because I have to activate it in the developer options.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
I dont know witch strange things happend to this poor phone.
But thank you for your reply.
Benny
Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...
enetec said:
Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...
Click to expand...
Click to collapse
What makes me suspicious is that it says "RETAIL" in the fingerprint but I have the German/Europe version. So it should be "RETEU".
Anyway, tried to flash the 7.1.1 retail stock rom because theres no reteu 7.1.1 available but the result is still the same: "Permission denied". But it was worth a try!
"Fastboot boot boot.img" doesn't work either. Bootscreen appears for a while, it vibrates and then goes back to fastboot.
I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Try flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
berka38 said:
I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Click to expand...
Click to collapse
How do I know whats the right version for my bootloader? Just by trial and error?
Ist there a list somewhere?
But yes, there is some hope rising inside me
EDIT:
I tried the rom you suggested already. It dowsn't work. Same error as always: Permission denied.
I got to check how I find my info what was on it later but it also gave me error when flashed but It booted
berka38 said:
I got to check how I find my info what was on it later but it also gave me error when flashed but It booted
Click to expand...
Click to collapse
Nope, tried it again. While flashing there are those known permission denied errors. When it should boot the "device is corrupt" screen shows up and it shuts down after a while.
But the slots changed somehow:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3760
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.274s
EDIT:
Uh, I noticed that the bootloader has also changed. Don't know whats happening here.
EDIT 2:
Is there a way to "hardbrick" the phone on purpose to do a blankflash?
bennyschw said:
Nope, tried it again. While flashing there are those known permission denied errors. ...<CUT>
Click to expand...
Click to collapse
Since what you posted you have an Oreo Reteu flashed on this phone. More, it is reported verity off and warranty void, so your bootloader should be unlocked.
My suspect is that someone has flashed it with Oreo THEN tried to relock bootloader and... bricked it! :silly:
Anyway, i don't know bootloader versions, but if this has been already flashed with Oreo, I don't think you will be able to reflash it with Nougat easily...
So, I would try this way...
- try to oem unlock it and look what it says...
- try to flash it with Oreo RETEU or Oreo Retail and look what happens...
What is weird is that "flashing locked" status...
You should try the lmsa tool first, see if it will do a rescue and get you back to booting.
https://support.lenovo.com/us/en/downloads/ds101291
If no go, then you can try a blankflash. It's possible that between all the flashing there have become discrepancies in the boot chain, and a blankflash will fix that. Afterwards you flash the correct firmware for your phone. You have an -06 Dual Sim right? So you'll probably want reteu ds firmware, but retail should also work. Either way it should boot, the only problem could be no modem. If that's the case, then factory reset from the recovery to see if that sorts it. If not, then flash the retail firmware and do a factory reset from the recovery, modem should be back.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
I would stay away from pie firmware until you're up and running. Just for verification it does say xt1789-06 by the charging port right? Does it have a dual sim try as well? Your priority should be, getting booting, sign into google, oem unlock. Once your bootloader is unlocked you'll have wiggle room, until then it'll be a little tough going.
Goot morning,
LSMA failes. It says "Fastboot flash single partition - Flash failes. Please try again.
When I do the oem unlock the phone replies:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.007s
Now I just tried to flash the boot.img of RETEU:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.541s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.547s
And RETAIL:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.538s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.544s
In my first post I was trying to flash the single sim version. Was my fault. But the same things happend there. This is a XT1789-06 with dual sim.
But as you said, it should have booted with no mobile connection.
By the way, fastboot oem blankflash doesnt work either:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Is there another way to go to blankflash?
I also tired the edl cable method. But it went right into bootloader.
Right now I'm setting up my old laptop with only USB 2 ports. Maybe theres a difference. I'll keep you up to date.
Thank you for your effort!
Benny
This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.
41rw4lk said:
This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.
Click to expand...
Click to collapse
Absolutely nothing has changed except the battery voltage
Tried all the different retail and reteu 8.0 versions but there changes nothing. I also tried to boot the roms via boot boot.img but no one worked.
LSMA replies with the same error as before.
Cant even change the slots manually:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=other
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.006s
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny
adb-fastboot_ver29.0.5
Attached is the latest adb/fastboot files pulled from androidsdk. It's weird that you can't even switch slots, so here is the latest files, just unzip to their own folder. Open folder, hold shift then right-click a blank area in the folder, open command window here. Try repeating the instructions in my last post and see if anything works this time around, use a 2.0 port if possible and use a port off the motherboard. Trivial it seems, but necessary for some. Double check the command fastboot --setactive="a,b, or other" could be "_a or _b" I don't use that command often so the syntax could be wrong, so try with or with the underscore_ or simply use 'other' w/o 'quotes' to switch slots. We're trying to get the slots as matched as possible so that if all else fails hopefully the lmsa tool will at least do a rescue on it. Right now I think you have bits and pieces of everything and lmsa sees it as something foreign or custom and won't touch it.
bennyschw said:
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny
Click to expand...
Click to collapse
I thought you were being funny until I looked at the serial no. in both posts... it the same f'n phone. Flashed to pie, f'd up, rolled back to oreo, bootloader locked, all kinds of wrong. Since it was on pie before, you'll need pie to fix it. Depending on what version of pie was flashed, you might need to wait for an update to roll out so you have a new enough firmware to overwrite the nv values. So there's that.
Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny
bennyschw said:
Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny
Click to expand...
Click to collapse
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots
danyfenton said:
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots
Click to expand...
Click to collapse
The same situation here, I am stuck in the bootloader because it indicates "Flashing_lock", I cannot enter the operating system to unlock because it says that the device is corrupt, I cannot change the slot in Fastboot mode, I cannot flash a new ROM, Neither the same ROM or the old ROM ... What do you think about forcing the EDL state, to try to recover with blankflash? (If I already tried the blankflash commands and do not allow them in the Fastboot, I would have to damage the cell phone on purpose but I don't know how)
and you haven't achieved anything yet have you?
mine is still standing here.
Hey everyone, since i tried updating my moto z2 force att with a faulty cable and then using a working one through lenovo "smart" "assistant", whenever i turn it off or restart i get: Fastboot reason: fall-through from normal boot mode, after trying many things the only way i found to recover my phone was to run this command list from adb command promt:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
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 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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot
I know that those commands are for installing a rom, but i was in a hurry and got away with it.
However i found that these commands are the needed to avoid losing all my data.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Please note that this is a temporary solution, if i turn off my phone i will have to run the commands again, which honestly i dont know what are they for .
If this helps someone, use it. If someone has a permanent solution, could you provide it? the bootloader cant be unlocked in the ATT phones as far as i know, couldnt find anything to help me on the internet.
If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.
thanks gotta try that one out.
What happens is that when i restart or turn on my phone, it says that it cant be trusted and wont boot, after a while it goes to the screen that i mention (havent figured out how to upload images here) where it says fastboot reason of the tittle of my post. From there the only way to interact is through adb with the commands that i mention.
41rw4lk said:
If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.
Click to expand...
Click to collapse
Hey i tried that one and no sucess only got this
https:// drive. google. com/ open?id= 1obn 0MW0qLBiMet9 -4oUwZVx X7j5UmT-Z
but if i turn it off it returns to the screens below
http s:// drive. google. com/ o pen?i d= 1ICNS -p1ZMCzp qJE6wAVM OlMEhO 2UuDVwand
htt ps: //d rive.go ogle .com/op en?id=1pfwLb JufMHPGS3klFw td6uWl1G gKIole
From there if i run the commands that i previously said i get this and if i reboot, the phone starts correctly
https ://driv e.goog le.co m/ope n?id=1RS aGOQfbo VkIY4u1 nLAHA9GWib5UK gJg
The rom that is in the adb folder is XT1789-04_NASH_ATT_8.0.0_OCXS27.109-47-20_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip, and i previously tried to install this before the lenovo smart software wasnt working at all. The results were the same only that i lost all my data.
If i try to run the lenovo smart assistant again and try to recover, it says that my phone is not supported, weird because that software caused all of this and the faulty cable :silly:
Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.
41rw4lk said:
Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.
Click to expand...
Click to collapse
Yes, its ATT, it has the logo at the back, its the XT1789-04, according to settings.
I ran the command that you said and i get this
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_att-316e620-190110
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BNP
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 9CF79D1A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080575347
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4077
(bootloader) iccid: 89014103270252580378
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_att/nash:8.0.0/OCXS2
(bootloader) ro.build.fingerprint[1]: 7.109-47-23/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.261.4.nash_att.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NUS_ATT
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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 May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_att-316e620-190110
(bootloader) git:xbl: MBM-3.0-nash_att-9869834-190110
(bootloader) gitmic: MBM-3.0-nash_att-9869834-190110
(bootloader) git:rpm: MBM-3.0-nash_att-b13e14f-190110
(bootloader) git:tz: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:hyp: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:devcfg: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib64: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:keymaster: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:storsec: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) gitrov: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: att
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.750s
I used this tutorial to install it previously, and got the issue that im mentioning in my post
https://www.getdroidtips.com/att-moto-z2-force-stock-firmware/
Anyone got a solution yet?
Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip
Awesome! it woked, tanks!
41rw4lk said:
Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.
mau22975 said:
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.
Click to expand...
Click to collapse
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.
41rw4lk said:
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.
Click to expand...
Click to collapse
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!
mau22975 said:
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!
Click to expand...
Click to collapse
Some general moto flashing info
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Hi,
I have a cedric xt-1675 with locked bootloader (i have a key to unlock and i tried unlocking it through fastboot it says its disable) and when I try to load into recovery mode it gave me error
FAILED TO PASS VALIDATION. BACKUP TO FASTBOOT
BOOTUP FAILED
I tried flashing firmware through fastboot white doing mfastboot flash partition gpt.bin
C:\Users\Abdul Rafy\Desktop\New folder\ar\boot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.077s
all other flash commands works fine except mfastboot flash partition gpt.bin
Thanks
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
TheFixItMan said:
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
Click to expand...
Click to collapse
thanks for the reply, I never have unlocked my device before it has locked bootloader since start. anyway, I have tried "fastboot oem unlock UNLOCK_KEY" it says enable oem unlocking from developer option and the problem is i couldn't get into phone not even into recovery just fastboot. It used to get stuck at moto logo but now when I try to boot normally it says
Failed to verify hab image boot
failed to validate boot image
Error: Failed to pass validation. backup to fastboot
Boot up failed
and if I try to go into recovery, it says
Failed to verify hab image recovery
failed to validate recovery image
Error: Failed to pass validation. backup to fastboot
Boot up failed
another thing I did try Software repair assistant but it gave me error on 47%
Here the getvar just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x4e
(bootloader) uid: 0295944600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-07-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 8: 2: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tescogb
(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
This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag
ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01u CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com
Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers
My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com
Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.