Database Users

Moto E4 XT1765 (MetroPcs) Super Hard-Bricked?

Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.

tboned82 said:
Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.
Click to expand...
Click to collapse
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app

@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.

madbat99 said:
@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.
Click to expand...
Click to collapse
Oh but I have unlocked the bootloader, I got a code and everything I followed all the instructions on this guide
HTML:
https://forum.xda-developers.com/moto-e4/moto-e4-qualcomm-roms-kernels-recoveries--other-development/guide-xt1766-stock-firmware-restoration-t3775347
as well as this one as well
HTML:
https://forum.xda-developers.com/moto-e4/how-to/complete-noob-guide-to-rooting-metropcs-t3701234
I ran into trouble when I formatted /data partition (just wiped it clean, without a way to boot into the system) I then followed the guide in the first link and I'm where I'm at now it's when I downloaded the files from the first link and started issuing the given commands in when oem-unlock when away and it was locked again. But yes I did have the device oem unlocked at one point.

whodisname said:
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.

tboned82 said:
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.
Click to expand...
Click to collapse
Glad you started a thread on this. There is a way out of this.
@kartik verma has a guide that can help you out on this. Since your bootloader is locked again it won't matter if you run the command to lock it back. However, with our variant you might have some trouble, so READ CAREFULLY steps 1-3.
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-stock-firmware-restore-t3661684
Things You Should Know Going Into It:
1. On our variant when you try to erase anything via fastboot is will say "PERMISSION DENIED". Run the command anyway and see what I mean - so you can effectively skip the ERASE PART of the guide. Instead, go straight to reinstalling over the files already there. It does that even when the bootloader is unlocked, and I have no idea why.
2. Download the firmware officially from Motorola from here:https://firmware.center/firmware/Motorola/Moto E4/Stock/ From there, download the following PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml.zip. It's the earliest one I know of that came on my phone that will not give you any problems flashing Magisk v14 later once you restore. Very important.
3. Extract the firmware to a single folder to your desktop. Makes it easier navigating later.
4. Download Minimal ADB and Fastboot. Don't use any other Fastboot. Trust and believe, its easier; Save Minimal ADB and Fastboot to your C:/ Drive.
5. In order to flash the files accordingly, you are going to have to pull firmware individual files (i.e. boot.img and system sparschunk files) to the Minimal ADB folder. Keep track of them.
6. You really only need to follow steps 1-3. Don't go past there.
---------- Post added at 03:52 AM ---------- Previous post was at 03:45 AM ----------
In my case when my phone hard bricked (wouldn't boot past recovery splash or the N/A splash) I could still get to fastboot. I flashed boot.img, and ALL of the system sparse chunk files. That brought me back enough to load recovery and delete everything and flash anew. However, If you think you've deleted the system, plus your bootloader is locked again you're probably going to have to reflash all of those files. I'd say as long as you have fast boot, reflash through fastboot boot.img, and every single system_sparsechunk files. Reboot and see what happens. If it doesn't work, keep on flashing until you re-restore the phone completely. If you start getting errors, refer to the rest of kartik's guide. (Steps 4- to completion) and ask me questions. There really isn't a definitive one size fits all variants for this phone - ours is special.
---------- Post added at 04:06 AM ---------- Previous post was at 03:52 AM ----------
Here is my getvar for you to see in comparison (I blocked off sensitive info like my IMEI and UID)
Code:
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-msm8917-BA.09(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY224GRCFF
(bootloader) cid: 0x0016
(bootloader) channelid: 0x8e
(bootloader) uid: ********00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *classified by order of your government*
(bootloader) meid:
(bootloader) date: 09-13-2017
(bootloader) sku: XT1765
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/perry_metropcs_c/perry:7.
(bootloader) ro.build.fingerprint[1]: 1.1/NCQ26.69-46/46:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.46.perry_metro
(bootloader) ro.build.version.full[1]: pcs_c.MetroPCS.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8917TMO_18.08.04.12R PERRY_NA_UMTS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g9acc907-0000
(bootloader) kernel.version[1]: 6-g486eb8a ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 20 09:51:52 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VBA.09-0-ge2011ab
(bootloader) rpm.git: git=MBM-NG-VBA.09-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) devcfg.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) keymaster.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib64.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) prov.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) aboot.git: git=MBM-NG-VBA.09-0-gcae5764-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs

Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me

tboned82 said:
Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me
Click to expand...
Click to collapse
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.

Articul8Madness said:
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.
Click to expand...
Click to collapse
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success

Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
Click to expand...
Click to collapse
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.

Moto E4 XT 1765 hard brick
Articul8Madness said:
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.
Click to expand...
Click to collapse
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache

Mirani said:
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
Click to expand...
Click to collapse
Let me see if I have this correctly.
You had a stock rom on your phone which you mentioned NCQ.
Then you connected your phone to the wifi.
Then you of your own volition took an update.
This update erased whatever you did trying to get root.
Then your phone bricked.
Now when you attach it to a PC it is showing HS_USB_Qdloader 9008
Is that right?
You need to pull the following firmware and try and flash it...PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml
I've never heard of your firmware. Try that firmware and flash it piece by piece and see if that gets you back working.

Hello, the same problem xt1765 metropcs HS_USB_Qdloader 9008, with that tool will get the firmware? Does not enter fastboot, help

If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader

TheLastAlphaUK said:
If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader
Click to expand...
Click to collapse
Again you are answering people with facts about the mediatek version, these ones have the Qualcomm version, therefore, SPflash tool does not apply

My bad cant I use the ADB sideload or update commands to reflash a stock firmware package. ? In kinda in a rush trying to answer all these questions I will look at it when I can sorry

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.

Moto G4 plus stuck in bootloader mode (Hard Brick)

Hi All.
I have unlock boot-loader and flash stock ROM after that i got an update (nougat 7.1) and I allowed.
after allowing my mobile stuck in bootloader and i am not able flash new images getting:
FAILED (remote failure)
finished. total time: 0.144s,
i tried all possible way.
for hard brick i followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but no success. please help me out.

If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.

echo92 said:
If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.
Click to expand...
Click to collapse
Below is the output of fastboot getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: d72acc4e
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: EC1CEC0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.104s
and i flash nougat 7 then i got update, I allowed update and phone got stuck in bootloader.

What firmware are you trying to flash now? Looks like your main issue is that you do not have a GPT partition table on your device, so your device does not know what files to flash.
I would recommend downloading the Oreo firmware from here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip delete the old stock ROM files from your ADB folder and replace with the Oreo firmware files. Then try to flash the Oreo GPT file

Stuck on bootloader with NO OS and OEM_LOCKED -- (MOTOG4PLUS)
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!

viking_vikram said:
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!
Click to expand...
Click to collapse
What happened to your device before this?
Which GPT.bin are you trying to load up? Try the April 2018 GPT and bootloader https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI or the December 2018 GPT and bootloader: https://drive.google.com/open?id=1TlFPYf4y3MEARFUuHSNB5Ty0GD-SQua-
However, if your device continues to report GPT partition initialisation errors, it's possible your flash storage is damaged and may require a motherboard replacement.

Where can I get a motherboard replacement ?
will it finally solve my problem ?

viking_vikram said:
Where can I get a motherboard replacement ?
will it finally solve my problem ?
Click to expand...
Click to collapse
Probaly a service centre would be the best place to request a motherboard replacement. It may solve your issue, however, as your G4 Plus is out of warranty, a motherboard replacement is not cheap - I've seen quotes for 8000-1000 rupees. Thus, you may wish to look into buying a new device altogether.

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,

Restore xt1965-t

I have an xt1965-t, not the t-mobile specific version.
I installed Lineage. It currently has the lineage recovery on it. It isn't rooted.
Is it possible to completely restore it to it's factory state? There is no data on it that needs to be preserved.

rob.aberth said:
I have an xt1965-t, not the t-mobile specific version.
I installed Lineage. It currently has the lineage recovery on it. It isn't rooted.
Is it possible to completely restore it to it's factory state? There is no data on it that needs to be preserved.
Click to expand...
Click to collapse
(Lenovo) MOTO Smart Assistant (PC)

sd_shadow said:
(Lenovo) MOTO Smart Assistant (PC)
Click to expand...
Click to collapse
I tried that but it doesn't seem to support this phone. It detects the phone but can't match a firmware to it.

rob.aberth said:
I tried that but it doesn't seem to support this phone. It detects the phone but can't match a firmware to it.
Click to expand...
Click to collapse
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
I am not sure I am seeing the firmware for my phone unless I am missing something.
Here is the device info:
Spoiler
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-05-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
(bootloader) battid: SB18C53460
(bootloader) battery-voltage: 4393
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21-18-4/67563:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Tue S
(bootloader) kernel.version[3]: ep 29 19:00:13 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:pmic: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200929
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:prov: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 5
It seems like I should look in the 'lake' 'retla' directory but the only firmware there is for the xt1965-2. I am thinking about it wrong?

rob.aberth said:
I have an xt1965-t, not the t-mobile specific version.
I installed Lineage. It currently has the lineage recovery on it. It isn't rooted.
Is it possible to completely restore it to it's factory state? There is no data on it that needs to be preserved.
Click to expand...
Click to collapse
Seems unlikely you have an XT-1965-T that is not T-mobile.
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
even if that is the case it should be ok using TMO firmware with bootloader unlocked.
Also there is a Moto G7 Plus Forum
Moto G7 Plus
The Moto G7 Plus is a 6.2" phone with a 1080 x 2270p display. The Snapdragon 636 is paired with 4GB of RAM and 64GB of storage. The main camera is 16MP and the selfie camera is 5MP. The battery has a 3000mAh capacity.
forum.xda-developers.com

rob.aberth said:
I am not sure I am seeing the firmware for my phone unless I am missing something.
Here is the device info:
Spoiler
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 11-05-2020
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
(bootloader) battid: SB18C53460
(bootloader) battery-voltage: 4393
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPW30.61
(bootloader) ro.build.fingerprint[1]: -21-18-4/67563:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Tue S
(bootloader) kernel.version[3]: ep 29 19:00:13 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200929
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:pmic: MBM-3.0-lake_retail-efaf0cccb-200929
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200929
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:prov: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200929
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 5
It seems like I should look in the 'lake' 'retla' directory but the only firmware there is for the xt1965-2. I am thinking about it wrong?
Click to expand...
Click to collapse
You have 2 conflicting lines
Code:
radio: TMO
ro.carrier: retla

If you are in the USA flash the TMO
If you are not in the USA flash the RetLA
If you flash the RetLA and you cannot connect to your carrier
Flash this from TMO
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

sd_shadow said:
Seems unlikely you have an XT-1965-T that is not T-mobile.
Click to expand...
Click to collapse
As I understand it the the phone was originally made by Motorola for t-mobile and sold as the Revvlry+. Recently, Motorola started selling them as the US version of the Moto g7 plus. Hardware wise I think they are identical.
sd_shadow said:
If you are in the USA flash the TMO
Click to expand...
Click to collapse
If I flash the TMO will it turn it into a revvlry+ and load all the t-mobile "stuff"?

rob.aberth said:
As I understand it the the phone was originally made by Motorola for t-mobile and sold as the Revvlry+. Recently, Motorola started selling them as the US version of the Moto g7 plus. Hardware wise I think they are identical.
If I flash the TMO will it turn it into a revvlry+ and load all the t-mobile "stuff"?
Click to expand...
Click to collapse
yes see post #8

sd_shadow said:
yes see post #8
Click to expand...
Click to collapse
So, I apologize if this a silly question since I am brand new to this but what I need to do if I understand from that post is follow all the instructions for flashing the retla and then before issuing the reboot I execute the 4 commands in post #8 but using the file versions from the tmo version. Is that right?

rob.aberth said:
So, I apologize if this a silly question since I am brand new to this but what I need to do if I understand from that post is follow all the instructions for flashing the retla and then before issuing the reboot I execute the 4 commands in post #8 but using the file versions from the tmo version. Is that right?
Click to expand...
Click to collapse
The radio commands can be flashed later.

sd_shadow said:
The radio commands can be flashed later.
Click to expand...
Click to collapse
In fact you can just skip these RetLA radio commands
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Then it shouldn't be an issue.

So...I was just about to start when I noticed that sparse chunks are bigger than my max-sparse-size. Is that something to worry about?

OK, thanks for all your help.
I went ahead and just tried it even with the max-sparse-size mismatch. It seems to have worked. The phone boots, connect to the mobile network and generally functions as factory new. I was also able to relock the bootloader.
The only issue is that remains is when the phone boots I get a nasty looking error message that reads: "Your device has loaded another operating system".
Is there any way to remove that or do I just have to live with it?

rob.aberth said:
OK, thanks for all your help.
I went ahead and just tried it even with the max-sparse-size mismatch. It seems to have worked. The phone boots, connect to the mobile network and generally functions as factory new. I was also able to relock the bootloader.
The only issue is that remains is when the phone boots I get a nasty looking error message that reads: "Your device has loaded another operating system".
Is there any way to remove that or do I just have to live with it?
Click to expand...
Click to collapse
Not likely.
You could try LMSA again.
But LMSA may be confused with the RetLA channel and the TMO radio

rob.aberth said:
OK, thanks for all your help.
I went ahead and just tried it even with the max-sparse-size mismatch. It seems to have worked. The phone boots, connect to the mobile network and generally functions as factory new. I was also able to relock the bootloader.
The only issue is that remains is when the phone boots I get a nasty looking error message that reads: "Your device has loaded another operating system".
Is there any way to remove that or do I just have to live with it?
Click to expand...
Click to collapse
Hi, I have the exact same device as you.
1) Did you just flash the full RETLA (XT1965-2) firmware from LoLinet? as-is? or did you need to modify radio stuff?
2) There apparently is a method to mask the nag message of "another operating system". It is to flash another modified logo . There a a couple discussions about it. Here is 1. https://forum.xda-developers.com/t/bootlogo-modded-bootlogo-from-unlocked-bootloader.3910421/

poog said:
Hi, I have the exact same device as you.
1) Did you just flash the full RETLA (XT1965-2) firmware from LoLinet? as-is? or did you need to modify radio stuff?
Click to expand...
Click to collapse
I flashed everything except the radio related stuff identified above using the instructions in the xml file.
poog said:
2) There apparently is a method to mask the nag message of "another operating system". It is to flash another modified logo . There a a couple discussions about it. Here is 1. https://forum.xda-developers.com/t/bootlogo-modded-bootlogo-from-unlocked-bootloader.3910421/
Click to expand...
Click to collapse
Thanks! I will check it out.