Database Users

Can't get past fastboot (XT1575)

So I just got one of these off my friend and I'm trying to get it up and running. I can't currently get past boot. If I let it go it boot loops, if I boot into recovery it boot loops... if I do anything other than "Boot loader logs", QR Codes or Restart bootloader it bootloops. I've spent the last 2 hours trying to find a solution around but I'm not finding anything close to what I need. I've tried the return to stock tool in the development section. It gets a bunch of errors when it's trying to flash stuff (Remote Failures). I can post that code if needed. I can get into fastboot but nowhere past it. I think the problem may stem from me having a locked bootloader (it's unable to be unlocked, already tried that on Moto's site). Is there any way I can unbrick this thing?
EDIT: Had formatting wrong on the unlock code. it is eligible. Waiting on the code now.
EDIT 2: Can't unlock because Allow OEM Unlock isn't on in dev options... but I can't get to dev options since I can't get into the OS... -.-
EDIT 3: Reading around it seems like I SHOULD be able to flash stock firmware even with a locked bootloader so long as it passes preflash verification. I've downloaded 18-8, 18-4 and 18_cid7 from here: https://androidfilehost.com/?a=show&w=files&flid=44735 which is where the official Motorola builds are hosted. None of them have passed preflash verification.
here's my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(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: TA394001K4
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 0782A0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355486060585298
(bootloader) meid:
(bootloader) date: 09-10-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Dec 11 23:50: 4 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-8/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.8.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g2c916d9 (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 Fri Sep 23 04:48:05 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.079s
Click to expand...
Click to collapse
Which, if I'm reading right says the current version is 18-8. Is it possibly due to carrier that it's not flashing?
Last Edit: Alright I give up. I've downloaded every one off the official page, over 7GB of images total. Not a single one passes pre-flash verification. This is so aggravating. If anyone could point me in SOME direction at all so I don't lose my mind I'd be forever greatful. I've filed for a warranty, fully expecting this to be unfixable. Will be sending it Monday.

This is your version:
(bootloader) ro.build.version.full[0]:Blur_Version.24.221.8.clark_retus
You have to wait for it or Nougat(flashable).
With locked BL you cannot do anything except warranty repair.
@TraMaI
Ps.
Retus - cid9 is for you.

So basically I have to wait for a version they haven't put out yet? How long does it usually take for them to post them?

Use the retus 18-8 version, do not flash bootloader.img or gpt.bin but continue through everything else.
Will probably bootloop first time, boot into recovery (after flashing it) and perform a factory reset, then reboot and give it a minimum 20 minutes.
BTW, Factory Reset Protection is active "(bootloader) frp-state: protected (75)", so you will need the last Google account used on that device to access it... otherwise it's a brick.

Cannot unlock relocked bootloader

The title says it all.
When i run the fastboot oem unlock <unique id> command,
it shows status 7 error.
cant get unlock data either. please help how do i unlock bootloader again

Have you booted the device into the operating system completely and gone into the Developer options re-enabled OEM Unlocking?
If that isn't it, unfortunately we have seen this in a small number of Moto devices (less than 1% I would say)... Once they are unlocked, then relocked, something happens and they can't be unlocked again. Sometimes after an OTA update is successfully applied they can be, but that isn't consistent either. Been an occasional problem with all retail Moto devices since the first Moto G & X models released in late 2013.
Out of curiosity... can you provide the output of "fastboot getvar all" and mask out your IMEI/MEID?

acejavelin said:
Have you booted the device into the operating system completely and gone into the Developer options re-enabled OEM Unlocking?
If that isn't it, unfortunately we have seen this in a small number of Moto devices (less than 1% I would say)... Once they are unlocked, then relocked, something happens and they can't be unlocked again. Sometimes after an OTA update is successfully applied they can be, but that isn't consistent either. Been an occasional problem with all retail Moto devices since the first Moto G & X models released in late 2013.
Out of curiosity... can you provide the output of "fastboot getvar all" and mask out your IMEI/MEID?
Click to expand...
Click to collapse
Yes, OEM Unlocking is enabled!
Damn, this is a very unlucky case I guess. I can't get my IMEI numbers up, and hence no SIM detection for me. I relocked the bootloader and gave it in for repairs at Moto, they said they won't cover it under warranty and quoted 80% of G5+'s retail price to install a new motherboard and get it fixed. So, I thought I would flash Pixel Experience 8.1 and flash stock modem as suggested by others, so tried to unlock it, and can't seem to get it unlocked. Meanwhile I have tried flashing stock fastboot files, but can't get IMEI to return. Is there any other solution?
Output of getvar all:
Code:
(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: 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: ZY2242HSP4
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 80FBE67800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *removed*
(bootloader) meid:
(bootloader) date: 03-19-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Nov 9 8:33: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: 25.137-92/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.281.9.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4524a37 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Nov 20 09:32:29 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VC0.8C-0-g22013cf
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(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: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.047s

Same issue
Hi brother, I have the same problem which you were facing. Please suggest me some solution for this kind of issue if you had solved with your device. I did not find any solution till now feeling sad ..Kindly help me bro..
Thanks

Could be worse, mine is greyed out no matter what I fastboot. I tried my original firmware for my EU device and all the way up to the latest, always grayed out. You win Lenovo, I quit messing with my android devices after this one, this device has been a total mess. All my issues began with 64bit Roms.

Cupcake 1.5 said:
Could be worse, mine is greyed out no matter what I fastboot. I tried my original firmware for my EU device and all the way up to the latest, always grayed out. You win Lenovo, I quit messing with my android devices after this one, this device has been a total mess. All my issues began with 64bit Roms.
Click to expand...
Click to collapse
I have fixed devices in a worse situation than this. But this truly beats an enthusiastic child out of me. Well done Lenovo indeed! I think Lenovo Service Center blocks the unlock key once submitted for repairing for which they ask 75% of the cost.

Bootlooping XT1622 with locked bootloader

As above, my XT1622, running the December security update, is bootlooping, and has been since installing that update. It doesn't boot into recovery either. I recently bought it second hand and hadn't got around to enabling USB debugging, so am limited in terms of what I can do with it. I've flashed the December 2017 Fastboot stock on it, but no change (and of course downgrading to a previous version of the bootloader wouldn't work as things stand).
Any suggestions would be gratefully received! I don't want to give up on the thing because there's obviously life left in it somewhere.

Ok, did you flash the update.zip with stock recovery or twrp?

It was the stock firmware flashable through Fastboot, so just followed that method manually - Fastboot is the only thing I can reach. I can't boot into recovery mode at all, it just loops.

How are you flashing the fastboot stock ROM, are you using a script or flashing each command manually? Can you verify each command is reporting [OKAY] after flashing?
Also, are you performing a full flash on the device (including fastboot erase userdata)?
If you can, it would be good to see a getvar all data, so we have an idea of the state of this device, given it was second hand:
1)Boot your device to the bootloader, attach to your computer via USB cable.
2)Open ADB on your computer, and type 'fastboot getvar all' without quotes into the ADB terminal. Press Enter.
3)Paste the output in a new post here - you may wish to omit the IMEI. The output should contain a list of your device variables.

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Try this, this is for flash bootloader and Qualcomm drivers by 0

Thanks for the help, all.
I flashed each command manually on Fastboot (couldn't get script to run, for whatever reason), each was reported OKAY. I included 'erase userdata' in there.
getvar all results:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223FFP8R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: 13E8080100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (redacted!)
(bootloader) meid:
(bootloader) date: 08-09-2016
(bootloader) sku: XT1622
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 24 21:50:49 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.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: M8952_70030.25.03.62.01R ATHENE_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g498cc0c (hudsoncm
(bootloader) kernel.version[1]: @ilclbld34) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Nov 23 09:34:10 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
all: listed above

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

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.