Database Users

Moto G4 Plus (XT1641) Android Nougat 7.0 Softbricked after installing SuperSu

I was trying to root my Moto G4 Plus (XT1641) (Dual SIM bought in Wallmart, Mexico), installed the superuser-zip file, but it never loaded. Heres the deatiled info:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(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: MSM8952
(bootloader) serialno: (**********)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x22
(bootloader) uid: B129A00000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354116070814435
(bootloader) meid:
(bootloader) date: 05-21-2016
(bootloader) sku: XT1641
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 14 10:46:36 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_LATAM_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retmx
all: listed above
finished. total time: 0.102s
-First, i had to get the unlock bootloader code from Motorola following the steps on the website
(1) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
(2) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
(3) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
And it was the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock (******************)
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.006s]
finished. total time: 0.007s
but, as it said in the las section, my device appears to succesfuly unlocked bootloader:
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
- Following the next post https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 i installled Minimal ADB and Fastboot on my pc, and flashed twrp-3.1.0-0-athene.img. BUT, I DIDN´T NOTICE THE WARNING ON TOP OF THE POST: "If you are on NPJ25.93-11/12/14 (non-soak test Nougat), you MUST flash the ElementalX kernel (link) after step 4. Make sure to backup the stock kernel before proceeding". (and honestly i have no f****** idea if i was on NPJ25.93-11/12/14). I finished installing that post's phh's SuperUser, and Voila!, it didn't worked
-After loking for any solutions to this issue, i've found this post: https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592 and tried rooting and tried typing echo SYSTEMLESS=true>>/data/.supersu on the TWRP's terminal and using it's SuperSU file.
-Also: I forgot to make an Backup on TWRP :crying: before installing my first superuser file
I can acces bootloader on my cellphone and TWRP witouth problem, so it's softbricked.
1: How can i finish rooting my device and make ti work? or
2: Is there any way i could reinstall the OS (nougat or Lollipop) using any recovery file, re-stock, re-lock or something?

Okay, a few things from what I see from your post:
You're on NPJ25.93-14/16 (from your getvar infor fingerprint), so that build requires ElementalX or another custom kernel. I think that requirement stands for any Nougat build on Moto G4 devices anyway, since Google appears to have enforced kernel security under Nougat.
Regardless, you'll need to flash a custom kernel to get any root solution (or somehow bypass dm-verity), else you won't be able to boot. You may be able to copy ElementalX (https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836) to a SD card, or use the 'adb push' commands from your adb terminal to push the file onto your device.
Then, you may be able to boot into TWRP, flash the ElementalX kernel, wipe your cache/Dalvik then reboot.
If your device boots, then you may wish to check if phh Superuser is still active.
If no root is present, reboot into TWRP and then flash phh Superuser.
If you still get bootloops or are unable to get ElementalX onto your device, you may wish to flash the stock Nougat ROM (same build as what you have currently) from here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This will wipe TWRP and any root present (as your kernel and recovery will be stock again), you do not have to re-lock your bootloader if you choose not to, and if you do not use 'fastboot erase userdata' and the OEM lock commands, you may be able to retain your data (though hopefully someone else can chime in on this point). However, for a stable system, I'd recommend using all the erase commands as listed (which potentially means losing your data)
EDIT - from toppits' post here (https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64), you may be able to use these commands for the fastboot ROM (may save your data if you choose to re-flash the fastboot stock ROM):
Code:
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
As always, you may have to erase your data if your system becomes unstable, but hopefully you may be able to boot and recover your data. You may then wish to continue on with your system as is or, after backing up your data, fully wipe and re-flash to get a stable system.

Unbrick Moto X Pure

Hello everybody!
I don't know is there any solution, but maybe you know how to solve it. I recently flashed (i know i'm stupid) nougat retla version of moto x pure with locked bootloader. Got everything erased (suppose it's really hard brick), but bootloader shows everything (bl, baseband, clark XT1575), and i can't reflash stock 6.0. How to solve it, please help me...:crying:

Unlock BL & and flash stock 6+ for your model.
You can also send it for warranty repair. @masterman775

dzidexx said:
Unlock BL & and flash stock 6+ for your model.
You can also send it for warranty repair. @masterman775
Click to expand...
Click to collapse
thanks, but i tried to unlock bootloader, motorola says my device doesn't qualify for bootloader unlocking. Is it complete brick?

This is comon mistake.
masterman775 said:
thanks, but i tried to unlock bootloader, motorola says my device doesn't qualify for bootloader unlocking. Is it complete brick?
Click to expand...
Click to collapse
This is comon mistake. Remember to erase the "(bootloader)" and all spaces from the code that you got from fastboot.
All moto x puré can be unlocked.
Enviado desde mi XT1575 mediante Tapatalk

Not all:
BL status engineering(1) - can't be unlocked. It isn't locked.
For unlock must have:
"Allow oem unlock" - dev options - on.
"Moto device id" - off.

Thank you very much guys for your help, I'll try all the best, I think it's gonna solve everything.:angel::good:

dzidexx said:
Not all:
BL status engineering(1) - can't be unlocked. It isn't locked.
Click to expand...
Click to collapse
Partially true. Contrary to popular believe that a Engineering Bootloader status is some special unlock (like HTC's S-OFF) it's more of a "kind of" unlocked... you cannot flash unsigned images (TWRP or custom ROMs), but you can downgrade with signed images. It is like partially unlocked. But once a device is in Engineering Bootloader mode, we do not have the capability (read as "knowledge") to put it back into Locked or Unlocked state.
I only clarify this because some people try to pass these devices off as special or unlocked, they are NOT the same as a bootloader unlocked device.

acejavelin said:
Partially true. Contrary to popular believe that a Engineering Bootloader status is some special unlock (like HTC's S-OFF) it's more of a "kind of" unlocked... you cannot flash unsigned images (TWRP or custom ROMs), but you can downgrade with signed images. It is like partially unlocked. But once a device is in Engineering Bootloader mode, we do not have the capability (read as "knowledge") to put it back into Locked or Unlocked state.
I only clarify this because some people try to pass these devices off as special or unlocked, they are NOT the same as a bootloader unlocked device.
Click to expand...
Click to collapse
So guys, i tried to unlock it, everything went allright BUT... i can't allow oem unlock without a rom, because it was flashed incorrectly...

dzidexx said:
For unlock must have:
"Allow oem unlock" - dev options - on.
"Moto device id" - off.
Click to expand...
Click to collapse
It's very bad, but i can't do it, i have no rom

What was your last version. Connect to pc and:
fastboot getvar all
@masterman775

masterman775 said:
So guys, i tried to unlock it, everything went allright BUT... i can't allow oem unlock without a rom, because it was flashed incorrectly...
Click to expand...
Click to collapse
What do you mean "everything went alright"? What did you do?

dzidexx said:
What was your last version. Connect to pc and:
fastboot getvar all
@masterman775
Click to expand...
Click to collapse
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57 PNM=016G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08403R53
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D726E8001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355486060916121
(bootloader) meid:
(bootloader) date: 10-28-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 10 5:44:20 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.390s
that's what i've got

acejavelin said:
What do you mean "everything went alright"? What did you do?
Click to expand...
Click to collapse
I got the code to unlock the bootloader, got the token from Motorola, but when i entered fastboot oem unlock *code*, i got a message: "allow oem unlock"

You can try, in this order:
1. Go to recovery mode, wipe data, cache, factory reset, reboot.
2. Flash 24...48-8 without bootloader and gpt.
3. Again 25...LatAm - this one was flashed incorectly? Only for unlocking bootlader.
4. Moto service center.
---------- Post added at 07:06 PM ---------- Previous post was at 07:06 PM ----------
@masterman775

dzidexx said:
You can try, in this order:
1. Go to recovery mode, wipe data, cache, factory reset, reboot.
2. Flash 24...48-8 without bootloader and gpt.
3. Again 25...LatAm - this one was flashed incorectly? Only for unlocking bootlader.
4. Moto service center.
---------- Post added at 07:06 PM ---------- Previous post was at 07:06 PM ----------
@masterman775
Click to expand...
Click to collapse
Yeah man I think second will help... I tried to flash stock with September security patch, which is outdated, maybe my current (18-16 - December patch) version is more actual

Yes but there isn't 48-18 for fastboot. @masterman775

dzidexx said:
Yes but there isn't 48-18 for fastboot. @masterman775
Click to expand...
Click to collapse
I found a decompressed version, now i need to separate it to "sparses"

I think I saw it. Maybe.
You don't need to sparse - fastboot should do it automatically. @masterman775

dzidexx said:
I think I saw it. Maybe.
You don't need to sparse - fastboot should do it automatically. @masterman775
Click to expand...
Click to collapse
So I've tried "unsparsed" variant and "sparsed". I always get pre-flash validation error

If I good remember - uploader also couldn't flash it with locked BL.
Sorry - point 4. @masterman775

Moto X Pure Edition (style) 2015 | XT1572 Retasia Got Stuck at bootloader

Hi There , Idont Know How To Say This In Normal Way But Idont know How , So I Will Go Right Through The Problem
I Got This Moto X Pure Edition (style) X1572 | Retasia
And It Was On Android 5 On Locked
I Didn't Know I Have To unlock It Before Flashing So It's Lock
so I Tried To Update The Phone With Frimware That I Grabbed For Frimeware Center But It Was The Wrong Region( La )So I Tried Another (Eu)
Then I Found The Right Region By This Code : fastboot Getvar All and I Found That My Phone Is For Asia but I Can't Flash it because Of Gpt Partiton or bootloader Or Boot ، every Time I get the same errors
To sum up i want These Questions Answered
1 - is There any File For Region Asia With Android 7
2 - does my Phone Supports Deep Flash Cable Or Can I Flash it with Deep Flash Cable and How I Make Deep Flash Cable For Moto
3 - If I Couldn't Flash it Can It be flashed With a Box (like z3x for Samsung)
Please Help as Fast As You Can Im In deep Pain By This Phone and the Phone isn't mine I have to Return it By Tomorrow (1/8/2018) so Please Help To Solve This Problem Thanks

Normally, we should unlock bootloader before flashing firmware.
With unlocked bootloader, you can flash firmware from other regions, low android version (5) to higher one (6 or 7).
When flashing a different region firmware, you should make a factory reset via Recovery.
You should give more infomation about the state of the phone: can enter bootloader, recovery mode or not; can turn on screen or not; how the PC shows when the phone is connected to PC.....

mr_5kool said:
Normally, we should unlock bootloader before flashing firmware.
With unlocked bootloader, you can flash firmware from other regions, low android version (5) to higher one (6 or 7).
When flashing a different region firmware, you should make a factory reset via Recovery.
You should give more infomation about the state of the phone: can enter bootloader, recovery mode or not; can turn on screen or not; how the PC shows when the phone is connected to PC.....
Click to expand...
Click to collapse
Hi My Phone Is On And Its Locked On Bootloader (State Is Locked) I Couldn't Flash Any Frimware My Phone Region Is Asia I Cant Enter Recovery Mode PC And PC Shows It In Fastboot Mode
By The Way Is There Any Way To Put This Phone On Test Point Or EDL?

When you connect the phone to PC, if it turns on and enters fastboot mode (the screen turns on, and you can see the android and phone information), it is reflashable. But the bootloader is needed to unlock (you can google this problem, it's easy to perform). Then you go to firmware.center, find rom Asia with android 7 and flash it to the phone.
If the lcd is not on when you connect to PC, here is the method: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

mr_5kool said:
When you connect the phone to PC, if it turns on and enters fastboot mode (the screen turns on, and you can see the android and phone information), it is reflashable. But the bootloader is needed to unlock (you can google this problem, it's easy to perform). Then you go to firmware.center, find rom Asia with android 7 and flash it to the phone.
If the lcd is not on when you connect to PC, here is the method: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
It turns on and boots to bootloader but I tried to unlock the bootloader but it says you should allow bootloader oem unlock in developer options , and I can't access that obviously

So you can try to flash the firmware without flashing gpt.bin; bootloader.img; boot.img; recovery.img
Or you can try to make an sdcard like the link I mentioned before. Insert it to the phone and try to flash the firmware then.

mr_5kool said:
So you can try to flash the firmware without flashing gpt.bin; bootloader.img; boot.img; recovery.img
Or you can try to make an sdcard like the link I mentioned before. Insert it to the phone and try to flash the firmware then.
Click to expand...
Click to collapse
This the problem I tried every rom I cloud but none of it worked

If the phone can enter bootloader, the easiest way is to flash the newest firmware to the phone for both situations: locked or unlocked bootloader. My Verizon Droid Turbo had been soft-bricked when it was on Android 5. When android 6 came, it resurrected.
If a firmware is successfully flashed to the phone, it can start up normally or be stuck at logo. If it is stuck, enter recovery mode and factory reset.
There is one last method with super high risk: break the bootloader then resurrected by sdcard. One of my phone has died before, so never use this method if you don't have experience.
I mentioned everything I know. If your phone does not start, you may need another one.
I'm sorry that it does not help

Can Any Buddy Find The Right Frimware Based On This Info For Me I Need It ASAP Thanks
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08305BXS
(bootloader) cid: 0x0007
(bootloader) channelid: 0x52
(bootloader) uid: B02FEA001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 352342070733563
(bootloader) meid:
(bootloader) date: 12-24-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 28 3:15:52 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :5.1.1/LPH23.116-18/22:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.18.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255309.10.01.68R FSG-8994-01.71
(bootloader) version-baseband[1]: _CLARK_EMEA_DSDS_CUST+SW_DFLT
(bootloader) kernel.version[0]: Linux version 3.10.49-perf-ge36128e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Jul 30 14:36:15 CDT 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retmea
all: listed above
finished. total time: 0.116s

No OTA updates and no support? Am I on stock ROM or .......???

My first G5 Plus was stolen June last year (2018). Because it was uncertain if the insurance would pay and the G5 Plus was replaced by the bigger G5S Plus at that time, I decided to buy a second hand G5 Plus.
I didn’t knew than what I do know now. Anyway, things looked good, latest security update (June 2018)
I knew the Oreo update was coming, so I didn’t wonder I didn’t get a security update. But in November I saw Oreo was released in my country (the Netherlands), so I started worrying. I didn’t receive one on OTA reteu channel.
Some three weeks ago I contacted Motorola support and they told me they couldn’t help me because the warranty was void. So I started reading on XDA.
I want to stay on stock ROM for now, until Motorola stops security updates, so probably mid this year?
I wanted to flash fastboot to Oreo, but then I read about 0 IMEI, problems with persist etc.
I tried the Lenovo Motorola Smart Assistant but that one says unsupported device.
I don’t want to brick my phone and I don’t know the status or how to update my phone to stock Oreo and be able to receive OTA updates. From what I know and can see the bootloader is locked, but I don’t know what happened to the phone when it was rooted, flashed, which version etc.
Can you please help me? It’s really appreciated.
Here’s my ADB output:
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot devices
XXXXXXX fastboot
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3B7E68F800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: IMEI number present XXXXXXXX
(bootloader) meid:
(bootloader) date: 07-06-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 25 21:41:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-92-14/16:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.331.16.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47e POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gf055b2e-0010
(bootloader) kernel.version[1]: 7-g516eb24 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 30 15:51:32 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.437s
C:\DATA\G5Plus\Minimal ADB and Fastboot>

Confused74 said:
My first G5 Plus was stolen June last year (2018). Because it was uncertain if the insurance would pay and the G5 Plus was replaced by the bigger G5S Plus at that time, I decided to buy a second hand G5 Plus.
I didn’t knew than what I do know now. Anyway, things looked good, latest security update (June 2018)
I knew the Oreo update was coming, so I didn’t wonder I didn’t get a security update. But in November I saw Oreo was released in my country (the Netherlands), so I started worrying. I didn’t receive one on OTA reteu channel.
Some three weeks ago I contacted Motorola support and they told me they couldn’t help me because the warranty was void. So I started reading on XDA.
I want to stay on stock ROM for now, until Motorola stops security updates, so probably mid this year?
I wanted to flash fastboot to Oreo, but then I read about 0 IMEI, problems with persist etc.
I tried the Lenovo Motorola Smart Assistant but that one says unsupported device.
I don’t want to brick my phone and I don’t know the status or how to update my phone to stock Oreo and be able to receive OTA updates. From what I know and can see the bootloader is locked, but I don’t know what happened to the phone when it was rooted, flashed, which version etc.
Can you please help me? It’s really appreciated.
Here’s my ADB output:
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot devices
XXXXXXX fastboot
C:\DATA\G5Plus\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8C
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 3B7E68F800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: IMEI number present XXXXXXXX
(bootloader) meid:
(bootloader) date: 07-06-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 25 21:41:19 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-92-14/16:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.331.16.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47e POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gf055b2e-0010
(bootloader) kernel.version[1]: 7-g516eb24 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 30 15:51:32 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8C-0-gcba6d5d
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.437s
C:\DATA\G5Plus\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You can update Oreo by fastboot, and you don't lose any IMEI or persist as your just upgrading it and you won't brick your device also.as you are upgrading, not degrading. So you won't brick your device.

riyan65 said:
You can update Oreo by fastboot, and you don't lose any IMEI or persist as your just upgrading it and you won't brick your device also.as you are upgrading, not degrading. So you won't brick your device.
Click to expand...
Click to collapse
Thank you for your quick reply.
Nice to hear that it's safe to update to stock Oreo. From what I read there's no difference anymore in stock rom for different channels and models, it this true?
So I can use any fastboot stock Oreo rom vor my XT1685 on RETEU channel?
So f.i. : POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And if so, is the procedure below the proper one to flash using fastboot?
- Download adb fastboot tool and extract it on C:/ drive
- Now extract the downloaded ROM file to the adb fastboot folder.
- Once you are finished, open the command window by holding the SHIFT KEY and Right Mouse click.
- Now you need to sideload the OTA Oreo file to your phone. To do that, execute the following commands
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata[/I]
- Wait for a couple of minutes, once it is done. Now reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
- Once the installation is completed, enjoy the Oreo build OPS28.85-17 on your phone.
Or should I do the relatively easy OTA update described in here: https://forum.xda-developers.com/g5-plus/how-to/download-official-moto-g5-g5-plus-t3848246
since I seem to be running Indian firmware (92 instead of the 93 which I should be running for Europe).
Or is this way riskier with loss of IMEI etc. ?
Thanks in advance for your answer.

Confused74 said:
Thank you for your quick reply.
Nice to hear that it's safe to update to stock Oreo. From what I read there's no difference anymore in stock rom for different channels and models, it this true?
So I can use any fastboot stock Oreo rom vor my XT1685 on RETEU channel?
So f.i. : POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And if so, is the procedure below the proper one to flash using fastboot?
- Download adb fastboot tool and extract it on C:/ drive
- Now extract the downloaded ROM file to the adb fastboot folder.
- Once you are finished, open the command window by holding the SHIFT KEY and Right Mouse click.
- Now you need to sideload the OTA Oreo file to your phone. To do that, execute the following commands
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata[/I]
- Wait for a couple of minutes, once it is done. Now reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
- Once the installation is completed, enjoy the Oreo build OPS28.85-17 on your phone.
Or should I do the relatively easy OTA update described in here: https://forum.xda-developers.com/g5-plus/how-to/download-official-moto-g5-g5-plus-t3848246
since I seem to be running Indian firmware (92 instead of the 93 which I should be running for Europe).
Or is this way riskier with loss of IMEI etc. ?
Thanks in advance for your answer.
Click to expand...
Click to collapse
If you don't want to lose your data then go for OTA update, or if you want a clean installation of Oreo you can go for fastboot.(OTA update (this one)won't be detected if the software channel is different).and if you flash a different channel then the update time is different(future updates).

riyan65 said:
If you don't want to lose your data then go for OTA update, or if you want a clean installation of Oreo you can go for fastboot.(OTA update (this one)won't be detected if the software channel is different).and if you flash a different channel then the update time is different(future updates).
Click to expand...
Click to collapse
It took a while before I had the nerve to update, but I tried yesterday evening. I figured the best option would be to do the OTA update as described here: https://forum.xda-developers.com/g5-...-plus-t3848246
It worked like a charm, it updated my XT1685 to OPSS28.85-13 with reteu channel. After checking I received the October 1st 2018 security update and after that December 1st security update.
I am at OPSS28.85-13-5 at the moment.
So OTA updates work again.
I also tried the Lenovo Moto Smart Assistant again, but that still says unsupported device.
Thanks for your help and I hope this post is helping others too.

Confused74 said:
I also tried the Lenovo Moto Smart Assistant again, but that still says unsupported device.
Thanks for your help and I hope this post is helping others too.
Click to expand...
Click to collapse
LMSA did not recognize my device either, now it does. Don't exactly remember but I think it started working after I used the QR scan to dock the phone. You may want to give it a try if you have not already.

SIM not found after flash stock 7.0

Hi.
I have flashed my moto x style mt1572 single sim using this guide:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
and this stock rom:
XT1572_CLARK_RETLA_DS_7.0_NPHS25.200-15-8_cid12_subsidy-DEFAULT_CFC.xml.zip
after flashing complete i get no sim slot detected. i was installed for dual sim device. then i installed the correct one:
XT1572_CLARK_RETLA_7.0_NPH25.200-15_cid12_subsidy-DEFAULT_CFC.xml.zip
i dont know what is the correct model for my device, but since there is just 2 stock firmware with android 7.0 and i was have this version in my OTA update, so i think this is the correct ROM.
but after installing this one, i got same problem. my baseband not found and IMEI is unknown.
i tried many solution that i found but doesnt work.
Did it fix if i flash a custom ROM??
sorry for my english.
thanks.

help me
any one can help me please????

One thing I discovered when tinkering with randomblame's LineageOS build is that when I flashed the Android 7 ROM on my Moto X Pure the modem did not properly install despite fastboot reporting success in flashing. I had to repeat flash it some five or six times before the SIM would be correctly detected as a GSM SIM so I could set the APN. I would try flashing the correct baseband for your device again, but repeatedly flash it as I did for the Moto X I have here.

Strephon Alkhalikoi said:
One thing I discovered when tinkering with randomblame's LineageOS build is that when I flashed the Android 7 ROM on my Moto X Pure the modem did not properly install despite fastboot reporting success in flashing. I had to repeat flash it some five or six times before the SIM would be correctly detected as a GSM SIM so I could set the APN. I would try flashing the correct baseband for your device again, but repeatedly flash it as I did for the Moto X I have here.
Click to expand...
Click to collapse
Hi.
thanks for your solution.
i am in trying fix it in last 3 days and i cant.
first i want to be sure that the ROM that i flashed is the correct one.
base on i was received the android 7.0 before and i have XT1572 single SIM, is it possible that the mentioned ROM is incorrect??
i have flashed LineageOS 14.1 but it freeze on logo and i can't try it. but i don't guess my problem fix by it at all.
OK now, your solution is that i flash my modem several times after i flashed the stock ROM?? this is mean that i repeat these commands ?? or just the (*) one?
Code:
fastboot flash modem NON-HLOS.bin *
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
edit:
this is my fastboot getvar all if it helps!
Code:
PS C:\Users\Yasser\Desktop> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA39101VSV
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 52C1EA001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358951060751668
(bootloader) meid:
(bootloader) date: 02-03-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 11 21:18:11 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retla/clark:7.0/NPH
(bootloader) ro.build.fingerprint[1]: 25.200-15/14:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.15.clark_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6ed6ce8-0000
(bootloader) kernel.version[1]: 4-gfc58252 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed May 10 09:12:54 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retfr
edit2:
i always receive this message after each command: (bootloader) has-slot:modem: not found
like below:
Code:
PS F:\rom> fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
Sending 'modem' (41723 KB) OKAY [ 0.924s]
Writing 'modem' OKAY [ 1.103s]
Finished. Total time: 2.040s
is this normal ??
thanks.

yasser93 said:
i always receive this message after each command: (bootloader) has-slot:modem: not found
like below:
is this normal ??
Click to expand...
Click to collapse
Slot not found errors are normal. Current versions of fastboot are designed for devices with seamless updates, and the Moto X doesn't have them.
Repeat flashing the modem means just the command "fastboot flash modem NON-HLOS.bin". You don't want to erase the partitions at all in doing this. Flashing the FSG is also not necessary.

Strephon Alkhalikoi said:
Slot not found errors are normal. Current versions of fastboot are designed for devices with seamless updates, and the Moto X doesn't have them.
Repeat flashing the modem means just the command "fastboot flash modem NON-HLOS.bin". You don't want to erase the partitions at all in doing this. Flashing the FSG is also not necessary.
Click to expand...
Click to collapse
I do it several times but nothing happens. is any other solution is exist???
thanks

yasser93 said:
I do it several times but nothing happens. is any other solution is exist???
Click to expand...
Click to collapse
Contact Lenovo.

Strephon Alkhalikoi said:
Contact Lenovo.
Click to expand...
Click to collapse
I do not know if i could share this link, but this is their answer
https://forums.lenovo.com/t5/Moto-X-Pure-Moto-X-Style/SIM-not-found-after-flash-stock-7-0/td-p/4404682

I don't see why sharing the link wouldn't be allowed. Nevertheless, the forums was not what I meant when I said to contact Lenovo. At this point the phone will likely need servicing at a Lenovo service center, and with the phone out of warranty that is something you have to pay for.

Finally Solved!!
i can't believe it. While I was completely disappointed, it fixed by simply flash this modem:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
:victory::victory::victory::victory::fingers-crossed::fingers-crossed::fingers-crossed::laugh::laugh:

hi there,
i have the same problem. my sister Huawei y9 prime is locked and she is no longer with us
what can i do to unlock it?
this is my email: [email protected]
help appreciated,