Should I bother upgrading from MM? - X Style (Pure) Q&A, Help & Troubleshooting

I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.

abense said:
I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.
Click to expand...
Click to collapse
I'd go with aicp or dirty unicorns personally. I think these roms are definitely worth the upgrade and they're both extremely stable. AICP has a thread here on xda. Called the Android Ice Cold Project...and dirty unicorns has a website and g+ page.

Okay, I decided to do this:
Moto X Pure Factory Firmware Nougat NPH25.200-22
Here's my batch commands (I removed the line where it erase's user data)
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
And then I downloaded the latest TWRP, 3.2.1.0
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.2.1-0-clark.img
fastboot reboot recovery
Performing a backup of everything onto my ext-sdcard.
Going with AICP, just like I did 2 years ago when I first got this thing.
installing this version: aicp_clark_n-12.1-NIGHTLY-20171213.zip
And open_gapps-arm64-7.1-nano-20171216.zip
Here goes...

SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip

abense said:
SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
I'd go magisk, it's so simple to flash, and passes safety net easily, it's such a Breeze, and definitely the way to go rather than superSU!

So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.

abense said:
So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.
Click to expand...
Click to collapse
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.

What's the part about bricking if I upgrade/downgrade modem firmware?

Code:
(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.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA394xxxxx
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
(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: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-29-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 30 21:11:20 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:7.0/NPH
(bootloader) ro.build.fingerprint[1]: 25.200-22/21:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.22.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ge617f58 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Aug 29 00:53:54 CDT 2017
(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 (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.016s

abense said:
What's the part about bricking if I upgrade/downgrade modem firmware?
Click to expand...
Click to collapse
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.

acejavelin said:
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.
Click to expand...
Click to collapse
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(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.52
(bootloader) product: clark

abense said:
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(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.52
(bootloader) product: clark
Click to expand...
Click to collapse
Does it work properly stock, before doing anything?

Need to use this
https://forum.xda-developers.com/showpost.php?p=74999345&postcount=1061

What if...?
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?

Bill720 said:
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?
Click to expand...
Click to collapse
As was said, it involves taking an OTA upgrade, not using a factory image... You're good there.

Related

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.

[SOLVED] [XT1572] Fully bricked or is there a solution ?

Hey there,
To make it short, the phone was rooted, bootloader unlocked, and it was on Resurrection Remix (don't know which one, it was Nougat 7.1.2).
I tried to restore it back to stock, lock the bootloader etc (following this guide : https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 which has files for xt1572 too ).
During the process, I got the error that a lot of people get about the Preflash validation error and yet i went through, except that I still locked at the end (I did not notice the Note about it below the command lines, I so regret it).
I also flashed the original Motorola logo (instead of "Bootloader is unlocked"), but I don't think this has anything to do with the fact that it got bricked (I can be wrong though).
Now, I can't access the phone through the cable. adb devices (with killing and restarting server) doesn't detect anything, I'm just stuck on the big Motorola logo splash screen.
Anyone has any idea on any possible way to unbrick it ? (I heard about qualcomm hsusb something but I'm just not sure where it can lead)
Thanks !
@pef6000
Bootloader is locked? What is status code...?
can't you use fastboot (from device turned off hold power + vol down) and flash stock motorola rom?
Hey there, thanks for your answers.
I can't access bootloader nor fastboot. adb doesn't show any device anymore.
I cannot even turn on or off the phone. It just reboots even if I long-press the power button. It just boots back up, and I can only leave it like this until battery is depleted.
Hold power, when screen turn off hold only vol-. It should go to bootloader.
Check and post here BL status. @pef6000
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Btw, if you will go to bootloader mode(locked) - you can only flash again stock 6.0.1(newest).
Without bootloader and gpt.
Check how many sparsechunks you have in zip file, I think from 0 to 11.
Sorry for being late. I tried that yesterday, but one problem after another, Windows died
I'll pass some time on it whenever I get the computer working.
I tried starting in BL and it worked !
I think the fact that it wasn't working before was due to the phone bootlooping directly on splash screen (maybe, I don't know).
Here, battery was dead since I couldn't turn it off. So I plugged the phone in while keeping vol- pressed, and it booted immediately in.
Couldn't get a hold of the status code though, the computer rebooted and crashed, so I had something else in mind, sorry :/
Anyway, I'll do that whenever I can, thanks for your help !
Here again. I accessed bootloader and I get :
AP Fastboot Flash Mode (Secure)
[…]
Console [NULL]: null
Battery OK (charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Before this problem, when I tried to flash everything, I have parsechunks from 0 to 8, not 11.
Now, I don't really know what to do. Should I do everything back again with a 6.0.1 zip ?
pef6000 said:
Should I do everything back again with a 6.0.1 zip ?
Click to expand...
Click to collapse
Yes.
Without bootloader, gpt and Don't lock BootLoader.
Hey.
I did it, didn't lock bootloader, didn't flash bootloader.img nor gpt.bin, but it still freezes on the splash screen logo. I suppose it woudn't take as much as 15 to 30 minutes to switch from that splash screen to any other screen.
The bootloader is still accessible, and I still have the same things (unlocked, status 3, etc).
Am I doing something wrong ? :/
What is your model and what rom are you flashing?
What do you have on pc after: "fastboot getvar all"? @pef6000
It's a XT1572, European (got it in France).
I'm trying to flash the one for XT1572 in the link with the instructions : https://dl.prazaar.de/?dir=Android/XT1572/Factory/6.0.1/MPHS24.107-58-5_September_2016
(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: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA3910197I
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 42C5D7001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...]
(bootloader) meid:
(bootloader) date: 11-12-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 6 10:58:55 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g0ec7138 (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 Tue Nov 3 05:05:40 CST 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-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 2/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retfr
all: listed above
finished. total time: 0.242s
Did you flash: boot, recovery, all sparsechunks(0-11), modem, all erases? Each command ended with OK? @pef6000
Yes, I did all of this, everything turns out ok except one error (the Preflash Validation).
Now that I read it again, the post says it happens on gpt.bin, except I didn't flash it as you said.
I just did it again and I get it again at this step :
> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41699 KB)...
OKAY [ 0.923s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
Do I also not flash the modem ? :/
EDIT :
Btw, the bootloader log on the phone says "Image is too large" after the "cmd: flash:modem" line.
pef6000 said:
It's a XT1572, European (got it in France).
Click to expand...
Click to collapse
You should edit your post and remove the IMEI number...
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
dzidexx said:
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
Click to expand...
Click to collapse
From the getvar output, the bootloader is on 6.0
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
Click to expand...
Click to collapse
on MPHS24.49-18-4... I would suggest using the same version or XT1572_CLARK_RETEU_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and NOT 6.0.1. The 6.0.1 versions were only for certain variants, and I do not know if the RETFR ones had that.
And don't skip the bootloader or gpt UNLESS they actually fail... It is best to do it like this:
Also, if possible boot into the factory recovery and perform a full factory reset before beginning.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 [Verify number of sparse chunks and make sure you are doing the correct #]
fastboot flash modem NON-HLOS.bin [May need to be done more 2 or 3 times to "take", make sure it returns an "OKAY"]
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
My 2 cents worth... hope it helps.
@acejavelin Oh damn, thank you. I thought I checked correctly but I didn't notice the IMEI in there.
Thank you both for your help. Phone booted up on original rom, I'm happy
I'll mark this post as Solved, but I have a quick question : Can I use the XT1575 logo.bin found here :https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Or is it better not to do so ?
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/boot-animation-logo-bin-t3558942 @pef6000
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
dzidexx said:
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/[email protected]
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
Click to expand...
Click to collapse
@pef6000 Any of these or the one you mentioned is fine.
Sorry for the late answer, I flashed the 18-8 in the end.
Thanks again, I'll mark this as solved !

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,

Bricked Moto G5 - Potter

Hi,
Good Morning All,
I have an old Moto G5+ (Potter, XT1686) which I use for streaming media. The phone was rooted and used to run Lineage / Pixel Experience ROMs and for some time it was rooted with Magisk.
I wanted to remove the root and return to official ROM and I followed all the published procedures but I am unable to get the system to boot.
If TWRP is installed - The phone reboots to TWRP despite installing all variants of Lineage / Pixel Experience.
If I try and install the official rom using fastboot commands the phone goes to the "no command" screen and remains stuck there.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
My fastboot getvar all output is as below:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2244SWST
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 7E5EF1BA00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358958067204534
(bootloader) meid:
(bootloader) date: 05-23-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Feb 21 20:41:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PS28.85-17-6-2/77e7:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.2.potter.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: M8953_46.55.07.90R POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7b625a0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Mon Mar 4 14:31:59 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.156s
Click to expand...
Click to collapse
Motorola Rescue and Smart Assistant is also unable to get me to boot; It goes to the "no Command" screen.
Any help would is appreciated !
Thanks.
Ravi

Categories

Resources