Database Users

Phone is Bricked. ADB won't recognize device on Windows 10.

I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.

vu45 said:
I do not have a custom recovery. Can however boot to regular recovery. Tried to use ADB but computer just won't recognize the device. Tried multiple different cables.
Click to expand...
Click to collapse
Can you tell us more about what's going and how you got to that point? And what device specifically?
What are you trying to do with ADB? It is really of no use at this point, can you access fastboot in the bootloader?

Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.

vu45 said:
Tried to return to stock for update. Afterwards it just doesn't boot. X Pure 1575.
Trying to ADB into some sort of usable rom. It goes into ADB but computer won't recognize. Phone doesn't even boot into an OS.
Click to expand...
Click to collapse
ADB only works after the OS is booted... Do you have a terminal capture of your flash attempt? And how long are you waiting on first boot, it can take 30 minutes for first boot sometimes.

I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.

vu45 said:
I do not unfortunately but it doesn't even boot into OS. It boots immediately into bootloader.
Click to expand...
Click to collapse
Connect into bootloader mode to pc.
In cmd type+enter:
fastboot devices
/If you will see SN continue/
fastboot getvar all
/Copy and paste here the answer from pc/
If no devices:
Reinstall drivers + minimal adb & fastboot & repeat steps.
/Uninstall all drivers and programs for android, reboot pc, install/

(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57 PNM=016G72
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA08403TSL
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 9362E5001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 358986064519224
(bootloader) meid:
(bootloader) date: 03-22-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5: EDFE69452203DA0709C2C09BF656C85D
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 8 16:59:17 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.062s

Continue in this state flashing stock rom. Here is how to:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Download xt1575.retus.24...18-8 from:
https://mirrors.lolinet.com/firmware/moto/clark/official/RETUS/ @vu45

Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?

vu45 said:
Got it to boot! Thank you so much sir. If you don't mind me asking what does this mean:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Still got it to boot however
Also what is the latest security patch?
Click to expand...
Click to collapse
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.

acejavelin said:
Those are related to devices that ship with Nougat, they have 2 software slots, basically fastboot is just telling you that there are not multiple slots found, which is true for this device, they are informational only.
Click to expand...
Click to collapse
Ah thank you. I was wondering why it kept popping up.

vu45 said:
Ah thank you. I was wondering why it kept popping up.
Click to expand...
Click to collapse
Yeah, it seems pretty handy... my understanding is that Nougat devices and newer have 2 (or more) software slots, one is active and one is a backup, and you can even tell the device which one is active via fastboot... currently it is only used for seamless updates, although some custom ROMs may use this as well but I don't own a device that shipped with 7.0 or never so I haven't looked into it.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/

Alcatel 5065n ADB it won't recognize bricked phone
I have the drivers installed and it shows up Android device manager, but however when I type in command ADB devices the phone doesn't show up in the list

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,

Moto G7 (Soft brick?)

Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(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:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(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: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss

Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
and the fastboot details? its like, corrupted?

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
Dont Work, Remove Error

Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?

WoKoschekk said:
Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?
Click to expand...
Click to collapse
Nope, i cant go to the Stock Recovery, and the fastboot boot twrp.img dont work.

if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Or try RSDlite or any Motorola repair software...

WoKoschekk said:
if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Gpt and bootloader don't installs, the remote error its back.

WoKoschekk said:
Or try RSDlite or any Motorola repair software...
Click to expand...
Click to collapse
i tried, the RSD, and not recognize the phone.

So, you can't do anything... I guess the only chance to fix your phone is a blank flash.
I'm sorry but I don't know how to do that.
It would be better for you to use the search function.
Good luck!!

GordinhoBr said:
Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(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:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(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: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss
Click to expand...
Click to collapse
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.

diegovmsouza said:
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.
Click to expand...
Click to collapse
send me you phone number.

Do you have access to Fastboot mode, right?

River blankflash is available on Tel$gram

HueyT said:
River blankflash is available on Tel$gram
Click to expand...
Click to collapse
On what now?

iamcubeman said:
On what now?
Click to expand...
Click to collapse
Telegram

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.