I've tried loads of ways to unlock my boot-loader but It hasn't worked. This comes up every time:
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.353s
MY DEVICE INFO:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(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: TA39100B7D
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 097DC0001E000000000000000000
(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: 358951060358225
(bootloader) meid:
(bootloader) date: 09-18-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 24 0:35: 8 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6898f68 (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 Sat Jan 30 17:52:24 CST 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.48-0-g8c942c6
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (275)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.418s
PLEASE HELP ME !
Where are you getting an error? At "fastboot get oem_unlock_data" or ????
Can you take a pic of the bootloader screen?
acejavelin said:
Where are you getting an error? At "fastboot get oem_unlock_data" or ????
Can you take a pic of the bootloader screen?
Click to expand...
Click to collapse
It said that when I typed fastboot get oem_unlock_data
I check everything
I installed the drivers correctly
I did the developer options settings
Do you have discord/skype so we can talk?
PapaKappa said:
It said that when I typed fastboot get oem_unlock_data
I check everything
I installed the drivers correctly
I did the developer options settings
Do you have discord/skype so we can talk?
Click to expand...
Click to collapse
Do you have OEM Unlocking enabled in Developer Options?
acejavelin said:
Do you have OEM Unlocking enabled in Developer Options?
Click to expand...
Click to collapse
Yes
PapaKappa said:
Yes
Click to expand...
Click to collapse
Pic of bootloader screen?
acejavelin said:
Pic of bootloader screen?
Click to expand...
Click to collapse
The command prompt or my phone?
PapaKappa said:
The command prompt or my phone?
Click to expand...
Click to collapse
Phone...
acejavelin said:
Phone...
Click to expand...
Click to collapse
how?
PapaKappa said:
how?
Click to expand...
Click to collapse
What does it say under the green battery status line?
acejavelin said:
What does it say under the green battery status line?
Click to expand...
Click to collapse
Device is LOCKED Status Code: 0
Software Status: Official
Transfer Mode: USB Connected
Factory reset and try again... If fastboot works, it works, there is no partial working.
acejavelin said:
Factory reset and try again... If fastboot works, it works, there is no partial working.
Click to expand...
Click to collapse
You got discord/skype so we can chat?
It does not work. I factory reset my phone.
PapaKappa said:
It does not work. I factory reset my phone.
Click to expand...
Click to collapse
Then you need to go to the official forums, there is a special place for unlocking issues. There is no trick or special way, there is only one way and if it doesn't work you need to take the official route. There is only one way to do it.
Related
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.
C:\adb>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.102s]
finished. total time: 0.103s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238RLPB
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 074B980000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 05-28-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 22 1:25:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.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[0]: M8952_70030.25.03.62.02R ATHENE_INDIA_
(bootloader) version-baseband[1]: DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-ge03508d-00131-g44
(bootloader) kernel.version[1]: 2576f ([email protected]) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version[3]: :58:16 CDT 2018
(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: unknown
all: listed above
finished. total time: 0.129s
Did you find a solution to this situation? I have the same problem ...
j_cesarbm said:
Did you find a solution to this situation? I have the same problem ...
Click to expand...
Click to collapse
I have same issue and Moto Service has refused to help.
If I am not mistaken, this is defect in OEM firmware, which is reason why they may be having issues with Oreo 8.1 upgrade. Someone at Moto has no keys for OEM boot loader. Earlier Alphadog would help, but now he says contact customer service.
Waiting to see if my assumption is correct. So far Oreo 8.1 OTA not received. Motorola web site also says it will no more receive security patches.
mang0sings said:
I have same issue and Moto Service has refused to help.
If I am not mistaken, this is defect in OEM firmware, which is reason why they may be having issues with Oreo 8.1 upgrade. Someone at Moto has no keys for OEM boot loader. Earlier Alphadog would help, but now he says contact customer service.
Waiting to see if my assumption is correct. So far Oreo 8.1 OTA not received. Motorola web site also says it will no more receive security patches.
Click to expand...
Click to collapse
How has Motorola service failed to help? They couldn't generate a code for you? It's possible that only a motherboard repair or replacement can fix the bootloader unlock problem, especially if there are parameters missing from the getvar info.
Our device is over 2 years old, and for our device was only slated to get 2 major updates and 2 years of security patches. Do you have an active SIM card in your device?
I gave up trying to fix it, sold it, and bought another.
echo92 said:
How has Motorola service failed to help? They couldn't generate a code for you? It's possible that only a motherboard repair or replacement can fix the bootloader unlock problem, especially if there are parameters missing from the getvar info.
Our device is over 2 years old, and for our device was only slated to get 2 major updates and 2 years of security patches. Do you have an active SIM card in your device?
Click to expand...
Click to collapse
I gave up trying to fix it, sold it, and bought another.
j_cesarbm said:
I gave up trying to fix it, sold it, and bought another.
Click to expand...
Click to collapse
That's the right decision. That could also be reason their Oreo update has failed miserably. No more security patches will be released.
Hi guys
So I had this phone for like 4 years and it was working fine till it battery got damaged and I replaced battery
After that it was working normally but it wouldn't charge the phone when the phone was off! My phone turned on everytime I plugged the charger in... But I didn't mind looked fine to me
Until last week that I forgot to charge my phone and got 0% and turned off! When I tried to charge it for hours it still showed 0% of charge! And something new came app called cqatest app and there was no network service! I don't recall exactly what I've done but somehow I used to solve this problem...
But the other day I dropped my phone on my bed which is a soft surface and it wasn't my first time doing it and didn't throw it from a long distance (1 ft)... Then the problem came back and now I can't solve it. I tried everything and every single method on this forum or other forums... And I can't take my phone to any repair shop because of this corona-virus situation...
ps: My phone turns on with its turbo charger but not charging and it show no service. As soon as I unplug the charger it turns off no matter how long been charging. I can go to bootloader but when chose Recovery Mode it show the moto logo for 1 second and turns off . In bootloader I can see Battery : OK (in green)
Hello? Is anybody there?
It's the first time so far I see a post doesn't get any respond after this while on xda forums
Please help me guys I'll appreciate that
nima-md said:
Hello? Is anybody there?
It's the first time so far I see a post doesn't get any respond after this while on xda forums
Please help me guys I'll appreciate that
Click to expand...
Click to collapse
Likely device was damaged.
Try LMSA'S Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
What do you get with
Code:
fastboot getvar all
Sent from my ali using XDA Labs
sd_shadow said:
What do you get with
Code:
fastboot getvar all
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
This is what I got
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: griffin
(bootloader) board: griffin
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223T4QX9
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: 8EBCEC8D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 01-09-2017
(bootloader) sku: XT1650-02
(bootloader) battid:
(bootloader) iccid: 89148000003153514174
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:25 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin_verizon/griffin:8
(bootloader) ro.build.fingerprint[1]: .0.0/OCL27.76-69-6-3/5:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.5.griffin_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R GVS
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7f9c96b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Sep 25 04:38:43 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=fae78d8-dirty
(bootloader) hyp.git: git=fae78d8-dirty
(bootloader) devcfg.git: git=fae78d8-dirty
(bootloader) keymaster.git: git=fae78d8-dirty
(bootloader) cmnlib.git: git=fae78d8-dirty
(bootloader) cmnlib64.git: git=fae78d8-dirty
(bootloader) prov.git: git=fae78d8-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.160s
nima-md said:
This is what I got
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: griffin
(bootloader) board: griffin
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223T4QX9
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: 8EBCEC8D00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 01-09-2017
(bootloader) sku: XT1650-02
(bootloader) battid:
(bootloader) iccid: 89148000003153514174
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:25 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin_verizon/griffin:8
(bootloader) ro.build.fingerprint[1]: .0.0/OCL27.76-69-6-3/5:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.5.griffin_ver
(bootloader) ro.build.version.full[1]: izon.verizon.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R GVS
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7f9c96b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Sep 25 04:38:43 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=fae78d8-dirty
(bootloader) hyp.git: git=fae78d8-dirty
(bootloader) devcfg.git: git=fae78d8-dirty
(bootloader) keymaster.git: git=fae78d8-dirty
(bootloader) cmnlib.git: git=fae78d8-dirty
(bootloader) cmnlib64.git: git=fae78d8-dirty
(bootloader) prov.git: git=fae78d8-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.160s
Click to expand...
Click to collapse
I don't see anything wrong there.
You could flash firmware with mfastboot
download newest firmware here
https://mirrors.lolinet.com/firmware/moto/griffin/official/VZW/
or if LMSA downloaded firmware you can use that.
see
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
sd_shadow said:
I don't see anything wrong there.
You could flash firmware with mfastboot
download newest firmware here
https://mirrors.lolinet.com/firmware/moto/griffin/official/VZW/
or if LMSA downloaded firmware you can use that.
see
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I've already done this too but problem still remains
nima-md said:
I've already done this too but problem still remains
Click to expand...
Click to collapse
try
Verizon's Motorola Update/Repair Assistant
https://forum.xda-developers.com/general/rooting-roms/verizons-motorola-software-upgrade-t4085295
sd_shadow said:
try
Verizon's Motorola Update/Repair Assistant
https://forum.xda-developers.com/general/rooting-roms/verizons-motorola-software-upgrade-t4085295
Click to expand...
Click to collapse
Can I use downloaded rom on this tool?
If yes how?
nima-md said:
Can I use downloaded rom on this tool?
If yes how?
Click to expand...
Click to collapse
Not that I know of.
Sent from my ali using XDA Labs
Hi im new on this forum...lets jump the the problems. (sorry i got the verbs wrong, im not english native speaker)
1st problem: cannot enter in recovery (if i select the option the phone turn off and the led starts blinking)
2st problem: cannot flash stock rom/firmware because the phone wont turn on. (already tried to flash with oem locked but give me errors linked to the oem)
3st problem: the phone didnt charge but the leds blinking, already disconnected the battery, plugged the phone then reconnect the battery, this only give me the "lightining" icon but doesnt charge. if i press the power button shows me the "lightining" likes if is charging
I dont know what to do anymore, with the oem locked i cant flash anything, its giving me headaches...thanks for reading, hope i find the solution
Update: (this is the error i got, already know its from oem, plus when finished the phone just goes off, and didnt charge, only led blink)
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.738s
cowb0y said:
Hi im new on this forum...lets jump the the problems. (sorry i got the verbs wrong, im not english native speaker)
1st problem: cannot enter in recovery (if i select the option the phone turn off and the led starts blinking)
2st problem: cannot flash stock rom/firmware because the phone wont turn on. (already tried to flash with oem locked but give me errors linked to the oem)
3st problem: the phone didnt charge but the leds blinking, already disconnected the battery, plugged the phone then reconnect the battery, this only give me the "lightining" icon but doesnt charge. if i press the power button shows me the "lightining" likes if is charging
I dont know what to do anymore, with the oem locked i cant flash anything, its giving me headaches...thanks for reading, hope i find the solution
Update: (this is the error i got, already know its from oem, plus when finished the phone just goes off, and didnt charge, only led blink)
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.738s
Click to expand...
Click to collapse
So not a solution?
cowb0y said:
So not a solution?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Update
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Click to expand...
Click to collapse
Update yesterday i found reading here how to get the correct version of the rom stock, and already flashed it.
the phone wont charge (only appears the lightning icon but never increase or show "%") wont turn on, and didnt enter in recovery mode. i thinks its problem of the battery beacuse i buy new one and doesnt fit at all in the phone (it lacks 1cm) (also the battery is 3010mAh, and g6plus is 3200mAh i think)
Anyways here what you asked for Again sorry for my bad english.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 2793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.184s
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.