Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
TheKillerMaxOfficial said:
Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
Click to expand...
Click to collapse
You relocked bootloader or it relocked it self?
sd_shadow said:
You relocked bootloader or it relocked it self?
Click to expand...
Click to collapse
it self
TheKillerMaxOfficial said:
it self
Click to expand...
Click to collapse
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 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: MBM-2.1-ocean_retail-7fd887897c6-200930
(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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
TheKillerMaxOfficial said:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 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: MBM-2.1-ocean_retail-7fd887897c6-200930
(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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
Click to expand...
Click to collapse
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
TheKillerMaxOfficial said:
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
sd_shadow said:
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
Click to expand...
Click to collapse
it won't let me boot twrp, I didn't have it installed as recovery
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
I don't know much about it and I don't know what else to do.
TheKillerMaxOfficial said:
it won't let me boot twrp, I didn't have it installed as recovery
Click to expand...
Click to collapse
Did you try
Code:
fastboot oem blankflash
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
If you can find something to solve my problem, I would be very grateful.
sd_shadow said:
Did you try
Code:
fastboot oem blankflash
Click to expand...
Click to collapse
waiting for device
TheKillerMaxOfficial said:
waiting for device
Click to expand...
Click to collapse
How is it listed in device manager?
sd_shadow said:
How is it listed in device manager?
Click to expand...
Click to collapse
does not appear
TheKillerMaxOfficial said:
does not appear
Click to expand...
Click to collapse
It's there, you need to search for it, it maybe hidden in a collapsed section
sd_shadow said:
It's there, you need to search for it, it maybe hidden in a collapsed section
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008 (COM3)
TheKillerMaxOfficial said:
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
Ok so it's in EDL mode
Try rebooting PC
sd_shadow said:
Ok so it's in EDL mode
Try rebooting PC
Click to expand...
Click to collapse
I already restarted it, what's next?
TheKillerMaxOfficial said:
I already restarted it, what's next?
Click to expand...
Click to collapse
try
[Guide] Recovering from a hard brick
This guide aims to recover your G7 power from a hard brick that leaves it in emergency download (EDL) mode. Will this work with my device? This should work on any device in EDL mode. To check for this mode, first try entering fastboot by...
forum.xda-developers.com
Related
is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
update i fix my problem following this steps
https://forum.xda-developers.com/showpost.php?p=80052655&postcount=117
thanks to sd_shadow for the help
zaxcast said:
is my first time rooting and i run into some problems with my xt1955-5.
the phone no longer recognizes the sim card and imei null appears when i check for the imei i have my phone rooted so i already check into the modem folder and carrier and there is no files there.
I would appreciate the help
Click to expand...
Click to collapse
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
thanks
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[*][Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
thanks bro i finaly fix it and dindt lost my root thanks
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Having this same problem I think, I can't check IMEI using *#0606# (Only Serial number appears and some barcode) nor can I see anything on Settings (Both IMEI are blank, MIN, PRL version and MEID are unknown), I can only check IMEI (IMEI1 only) using "fastboot getvar all". I already tried flashing NON-HLOS.bin, erasing modems and flashing fsg, but still doesn't work. It stopped working some time after I had failed installing custom ROMs and went back to stock (I'm almost 100% sure it was working then after a few days it stopped working, it also stopped on an unrooted Moto G7 Play but still works on a Custom ROM+Magisk Moto G5)
https://forum.xda-developers.com/g7-power/help/sim-card-stopped-t4040745
https://forum.xda-developers.com/g7-power/help/lock-bootloader-oem-unlocking-t4051605 (I only ever flashed stock using eraseandupdate.bat and this thread, so it wasn't caused by "fastboot erase all". I did flash RETUS once (my device is RETBR), but that's after it'd stopped working already)
sd_shadow said:
Did you flash a different rom?
What have you done with root?
Most likely you need to reflash stock firmware
See fixing imei issues in
[Index]Motorola Flashing Utilities, Firmware, and more
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.
crazyc5127 said:
so i am having a similar issue, unknown baseband, IMEI. I did try the flash of NON-HLOS.bin and fsg.mbn but did nothing. and i wasnt able to do a backup before the phone hard bricked. i did use blankflash to recover the phone from the hardbrick. then i found that pp029.114-63_cid50 worked to restore my phone to boot up the system.
Click to expand...
Click to collapse
What does
Code:
fastboot getvar all
Say?
sd_shadow said:
What does
Code:
fastboot getvar all
Say?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s
crazyc5127 said:
What does
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326F5PS2
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: BF35179D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359527093352077
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 10 14:11:44 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:9/PPO29.114-6
(bootloader) ro.build.fingerprint[1]: 3/6c5d7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.21.72.ocean.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld107) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ma
(bootloader) kernel.version[3]: r 22 09:36:59 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-5dc80a2-200210
(bootloader) rpm.git: MBM-2.1-ocean_vzw-22daab3-200210
(bootloader) tz.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) prov.git: MBM-2.1-ocean_vzw-d9613e6-dirty-200210
(bootloader) aboot.git: MBM-2.1-ocean_vzw-7a20abd-200210
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.723s
Click to expand...
Click to collapse
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs
sd_shadow said:
You used the metro pcs firmware?
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?
crazyc5127 said:
i think it was just a blank firm to be honest. which of those firmware should i download and flash? the newest, right?
Click to expand...
Click to collapse
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
just finished the flash, i am able to see all the barcodes with *#06#. thank you for the proper link, searching on my own was close but still off just a little bit.
now, my end goal for this phone is to take it off the Metro network and have it on T-Mobile network directly. i recently upgraded providers, but got a phone that, to me, isnt quite as good as the G7 Power, the REVVlry Plus. its still a great phone, as it is a moto build, but the battery is what has me not wanting to use it. any pointers on going this route? i would like to have root access as well, so i can tune and tinker more.
https://mirrors.lolinet.com/firmware/moto/ocean/official/MetroPCS/
this is what i ended up using to get my phone back to life. now the phone sits at just having an unlocked bootloader.
my goal for this phone is to remove the Metro firmware and replace it with tmobile firmware. or root to be able to use any sim card.
sd_shadow said:
Yes, it's not unusual to need to reflash firmware after using a blankflash.
Use the newest.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
You should never use the firmware to rescue your phone, that was the problem at first place to lose your baseband. Use last known working firmware to rescue
please help I can not flahsear any firmware all come out error that can be .
I had installed rom CrDroid, I went to act to the ultma version after I made a wipe of everything and when I restart I presented this problem I
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-191212
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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) serialno: ecb1016
(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: 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: MBM-2.1-ocean_retail-0ff2029-191212
(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
all: listed above
Finished. Total time: 0.859s
Teriuz said:
please help I can not flahsear any firmware all come out error that can be .
I had installed rom CrDroid, I went to act to the ultma version after I made a wipe of everything and when I restart I presented this problem I
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff2029-191212
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(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) serialno: ecb1016
(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: 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: MBM-2.1-ocean_retail-0ff2029-191212
(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
all: listed above
Finished. Total time: 0.859s
Click to expand...
Click to collapse
your bootloader is locked
timba123 said:
I have the same problem XT1955-5 metro pcs G7 power. I had rooted it. After forgetting the copy partitions zip I'm stuck in AP Fastboot mode. I had oem unlocked bootloader already. Now it some how relocked. No unlock data can be read. Smh. I've tried blank flashes. I've tried lenovo rescue and my device isn't supported. I've tried various batch file flashes on windows. I've tried RSD lite. I know Samsung you can flash signed oem images with locked bootloader. Why can't lenovo or RSD flash them? I have QPST and Qfil but don't know how to use them or get the mbn programmer and various images or XML or patch files etc. Any ideas? I'd gladly donate on the 3rd of August
Click to expand...
Click to collapse
Dose up PC recognize the phone when pluged in
timba123 said:
In blank flash mode its Qualcomm loader
And fastboot works but phone seen as adb interface?
Click to expand...
Click to collapse
Can u put phone I to fastboot with the key combo
timba123 said:
It's a weird fastboot mode. Its stuck there. I can get to it from blank flash mode.
Click to expand...
Click to collapse
What dose it day in device manager on PC
timba123 said:
When it's in AP Fastboot Mode (secure) its motorola adb interface
When it's in blankflash mode its Qualcomm HS-USB QDLoader 9008 com17
Click to expand...
Click to collapse
Can u do any fastboot comands?
timba123 said:
Yes.
Click to expand...
Click to collapse
Can u type. Fastboot devices in terminal and tell me what it says
timba123 said:
a83507ca fastboot
Click to expand...
Click to collapse
Good deal I'm giving u an address for your stock firm ware https://mirrors.lolinet.com/firmware/moto/
roadkill42 said:
Good deal I'm giving u an address for your stock firm ware https://mirrors.lolinet.com/firmware/moto/
Click to expand...
Click to collapse
And this file rename it take off the zip and put bat ok
roadkill42 said:
And this file rename it take off the zip and put bat ok
Click to expand...
Click to collapse
What location is your adb folder?
roadkill42 said:
What location is your adb folder?
Click to expand...
Click to collapse
Once u downloaded the firm ware put it in ur adb folder then extract it in there and put that file I sent u in there make sure it take off the zip and put in bat ok once file and rom in adb folder look for the ocean fastboot . bat file make sure phone is still in fastboot. Also go to property of the bat file go to security tab and at bottom see if it says locked click it to unlock it then in adb folder click the bat file and sit back watch it run about 20im or less
---------- Post added at 05:40 AM ---------- Previous post was at 05:38 AM ----------
timba123 said:
Do I put the stock rom and bat files in the platform tools folder with fastboot and adb?
Click to expand...
Click to collapse
Yes I have mine on root of c and I used the minuim adb install any ways it only work if bat file is in same folder as adb and extracted rom
---------- Post added at 05:43 AM ---------- Previous post was at 05:40 AM ----------
roadkill42 said:
Once u downloaded the firm ware put it in ur adb folder then extract it in there and put that file I sent u in there make sure it take off the zip and put in bat ok once file and rom in adb folder look for the ocean fastboot . bat file make sure phone is still in fastboot. Also go to property of the bat file go to security tab and at bottom see if it says locked click it to unlock it then in adb folder click the bat file and sit back watch it run about 20im or less
---------- Post added at 05:40 AM ---------- Previous post was at 05:38 AM ----------
Yes I have mine on root of c and I used the minuim adb install any ways it only work if bat file is in same folder as adb and extracted rom
Click to expand...
Click to collapse
Then type fastboot devices before u start to make sure PC sees phone then close terminal then in ur adb folder look for the bat file make sure it renamed take off zip and put bat I noticed in the getall your bootloader is locked if this flashes u need to unlock bootloader . Well I'm hitting bed time come back here to let us know if worked or not ?
timba123 said:
Remote failure invalid partition name etc etc
Click to expand...
Click to collapse
Have screen shot of the terminal on PC and do u use tellagram? And do u have the TWRP image if so make sure PC finds phone then typ this fastboot boot (and the name of recovery img) if all goes well you should be in TWRP if thats the one u use I use ofox if that works u should be able to do factory reset then try to install costm rom try this type getval all send me screenshot of the out put of the terminal
timba123 said:
Remote failure invalid partition name etc etc
Click to expand...
Click to collapse
From what I see bootloader is locked do u have screenshot of the error from the flashing error?
timba123 said:
Everything invalid
Click to expand...
Click to collapse
Hmm try this in fastboot -w then typ fastboot reboot ok try this later then post back I'm going to talk to someone to find out what else to do night night
timba123 said:
Idk
Click to expand...
Click to collapse
https://www.getdroidtips.com/install-use-qualcomm-flash-image-loader-qfil/this looks like ur only option in ur fast boot screen on the phone showing bootloader locked u in us and what carrier u on
Have u tried to go to tellagram group Moto g7 power suport group there is most likely be able to help they more active I'm there as road kill try it out u just need the right firmware to get u going
---------- Post added at 06:08 PM ---------- Previous post was at 05:21 PM ----------
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This hopefully get back into regular bootloader screen after the 120 secs 2 min realse keys to see what happens then post Bak here
timba123 said:
Thanks to Telegram group I was able to fix with blankflash. I flashed stock RETUS to my MetroPCS variant with no issues.
Click to expand...
Click to collapse
can you give me your telegram? I have the same problem and still can't solve it
Has anyone found the solution? I have the same problem.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: cfa3ac35
(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-0ff20295b20-200404
(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
all: listed above
Finished. Total time: 0.250s
Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(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-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
motog7help said:
Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(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-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
I don't believe there is much hope.
There is some instructions for flashing with a locked bootloader in my thread
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Also some instructions for RSD Lite
You need Windows 7 or old for RSD Lite
For any flashing with locked bootloader you need the correct firmware
The getvar all has a lot of missing info
I'm not sure which firmware channel is the correct one.
There is a RetGB but I don't know if its dual sim
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETGB/
Or it could on one of the EU channels
Like RetEU2
Sent from my ocean using XDA Labs
Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance
motog7help said:
Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance
Click to expand...
Click to collapse
All I need is to run a blank flash which will get u back up and running
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
roadkill42 said:
All I need is to run a blank flash which will get u back up and running
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/. Go here and u cans find the blank flash
Thank you - I have tried a blank flash as well, but after running the .bat file, it unfortunately it just hangs on 'waiting for device' I think it is because the phone is not detected as an adb device (I didn't have usb debugging enabled when it broke).
From a quick google it looks like there's no way to change this from fastboot - does anyone have any tips for applying a blank flash when phone is not listed as an adb device on the console? (As I mentioned in the original post, under device manager it is showing up as 'Motorola ADB Interface')
U need the quilt com drivers installed to pc and the moto usb drivers
roadkill42 said:
U need the quilt com drivers installed to pc and the moto usb drivers
Click to expand...
Click to collapse
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?
motog7help said:
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?
Click to expand...
Click to collapse
You cannot use a blankflash unless the device is in emergency download mode (EDL)
To my knowledge the is no way to enter EDL with a locked bootloader.
Sent from my ocean using XDA Labs
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help
Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
sd_shadow said:
Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?
motog7help said:
Sure try
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?
Click to expand...
Click to collapse
RSD Lite using a Windows 7 or older PC
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs
https://www.5g-m.com/en/micro-usb-datacable-for-android/17894-edl-cable-w230.html is said to work
Thank you - I will give both of these a try and report back!
motog7help said:
Thank you - I will give both of these a try and report back!
Click to expand...
Click to collapse
Are u able to get into the quialcom minue using the volume bottons?
can someone help me with advice to get booting again
it was oem unlocked before fail to boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY323W4FKR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: C82C277300000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359525091092315
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-17-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28957
(bootloader) iccid: 89148000005008330805
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Oct 1 5: 5:18 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QCOS30.85-
(bootloader) ro.build.fingerprint[1]: 18-6/691ed:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Sep 30 23:2
(bootloader) kernel.version[3]: 2:14 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-a30e356d6d-200930
(bootloader) rpm.git: MBM-2.1-ocean_vzw-20f2cf34-200930
(bootloader) tz.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) prov.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) aboot.git: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: comcast
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P237
all: listed above
finished. total time: 0.307s
roadkill42 said:
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help
Click to expand...
Click to collapse
Thx, this command save me phone.
So I tried flashing some gsi's and they were great other than the fact they never work with verizon(which I have). So I decided to try to rescue and go back to stock but its not reading it as the Edge. I also have tried manually flashing the .imgs but the system imgs fail to flash. Does anyone have any knowledge of what can be done to recue the phone? Thanks in advance.
JimmyJurner said:
So I tried flashing some gsi's and they were great other than the fact they never work with verizon(which I have). So I decided to try to rescue and go back to stock but its not reading it as the Edge. I also have tried manually flashing the .imgs but the system imgs fail to flash. Does anyone have any knowledge of what can be done to recue the phone? Thanks in advance.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[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:
What does getvar all say?
Code:
fastboot getvar all
[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
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) product: racer
(bootloader) board: racer
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA5G
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0109
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227SPW6K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 7AA2E144
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 35552611
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-16-2020
(bootloader) sku: XT2063-2
(bootloader) carrier_sku: XT2063-2
(bootloader) battid: SB18C66911
(bootloader) battery-voltage: 3796
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: Android/treble_arm64_bvN/phhgsi_ar
(bootloader) ro.build.fingerprint[1]: m64_ab:10/QQ3A.200805.001/201230:u
(bootloader) ro.build.fingerprint[2]: serdebug/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.13.r1-08200-SAIPAN.0
(bootloader) version-baseband: M7250_HI205_55.222.01.30R RACER_NA5G_CUST
(bootloader) kernel.version[0]: Linux version 4.19.81-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Mon Sep 28 13:3
(bootloader) kernel.version[3]: 8:52 CDT 2020
(bootloader) git:xbl: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:xbl_config: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:abl: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) git:aop: MBM-3.0-racer_retail-51bfe71-200928
(bootloader) git:tz: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:hyp: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:devcfg: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:keymaster: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:storsec: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:uefisecapp: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) gitrov: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:qupfw: MBM-3.0-racer_retail-6ee337d-200928
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(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: 3
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86464
all: listed above
Finished. Total time: 0.499s
JimmyJurner said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) product: racer
(bootloader) board: racer
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA5G
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0109
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_SAIPAN 2.0
(bootloader) serialno: ZY227SPW6K
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 7AA2E144
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355526110607947
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-16-2020
(bootloader) sku: XT2063-2
(bootloader) carrier_sku: XT2063-2
(bootloader) battid: SB18C66911
(bootloader) battery-voltage: 3796
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: Android/treble_arm64_bvN/phhgsi_ar
(bootloader) ro.build.fingerprint[1]: m64_ab:10/QQ3A.200805.001/201230:u
(bootloader) ro.build.fingerprint[2]: serdebug/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.13.r1-08200-SAIPAN.0
(bootloader) version-baseband: M7250_HI205_55.222.01.30R RACER_NA5G_CUST
(bootloader) kernel.version[0]: Linux version 4.19.81-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Mon Sep 28 13:3
(bootloader) kernel.version[3]: 8:52 CDT 2020
(bootloader) git:xbl: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:xbl_config: MBM-3.0-racer_retail-213760469-200928
(bootloader) git:abl: MBM-3.0-racer_retail-d0a492fa0b-200928
(bootloader) git:aop: MBM-3.0-racer_retail-51bfe71-200928
(bootloader) git:tz: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:hyp: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:devcfg: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:keymaster: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:storsec: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) git:uefisecapp: MBM-3.0-racer_retail-2b63c82-200928
(bootloader) gitrov: MBM-3.0-racer_retail-823bb5f9-200928
(bootloader) git:qupfw: MBM-3.0-racer_retail-6ee337d-200928
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(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: 3
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86464
all: listed above
Finished. Total time: 0.499s
Click to expand...
Click to collapse
Lmsa likely not working because of this
Code:
bootloader) ro.carrier: unknown
You are flashing racer/RetUS?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow said:
Lmsa likely not working because of this
Code:
bootloader) ro.carrier: unknown
You are flashing racer/RetUS?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
JimmyJurner said:
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Can you post the servicefile.xml ?
As an attachment if you can.
sd_shadow said:
Can you post the servicefile.xml ?
As an attachment if you can.
Click to expand...
Click to collapse
That file?
JimmyJurner said:
Yes and the error message is "the device missed ro.carrier" in the smart asst.
this is the outcome of trying to fastboot flash
fastboot flash system C:\ProgramData\LMSA\Download\RomFiles\RACER_RETAIL_QPD30.114_80_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml\super.img_sparsechunk.0
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I'm not familiar with super.img, but the service.xml says
Code:
<step MD5="66475a16cefbb5f6bbaebfcf23defd25" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
which if flashing manually should be: fastboot, operation, partition, filename
Code:
fastboot flash super super.img_sparsechunk.0
Every time you are going to flash a new firmware you should be looking at the service.xml to see the current commands, they do change from time to time.
or use Rootjunky's Batch Script.
Easy way to create a batch script for flashing firmware
RSD_Lite_Motorola_XML_To_Batch_Script.zip
[Video]How to Firmware Restore your Motorola Device on Windows 10 without RSDlite by RootJunky
sd_shadow said:
I'm not familiar with super.img, but the service.xml says
Code:
<step MD5="66475a16cefbb5f6bbaebfcf23defd25" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
which if flashing manually should be: fastboot, operation, partition, filename
Code:
fastboot flash super super.img_sparsechunk.0
Click to expand...
Click to collapse
I'm going to give it a try now. If all fails I'll just make a flash all.bat and see if that works. Thank you for all your help! I know what you mean about the super.img. Things keep changing once you get used to it it changes again...
JimmyJurner said:
I'm going to give it a try now. If all fails I'll just make a flash all.bat and see if that works. Thank you for all your help! I know what you mean about the super.img. Things keep changing once you get used to it it changes again...
Click to expand...
Click to collapse
I've done some searching and Super does appear to be the new partition.
Code:
fastboot flash super super.img_sparsechunk.0
sd_shadow said:
I've done some searching and Super does appear to be the new partition.
Code:
]
fastboot flash super super.img_sparsechunk.0
Click to expand...
Click to collapse
That way did end up flashing!
So I took a flash all from my other motos firmware and modded it from 14 super.img to the 7 for this device moved all the files over started the bat file and my phone is stock once again. I think I'll be staying stock from now on(rooted of course)!
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Yasai1204 said:
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Click to expand...
Click to collapse
What does getvar all say? (remove imei before posting it).
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nio_retail-6b3ddf45a7d-210503
(bootloader) product: nio
(bootloader) board: nio
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SUPER
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB KIOXIA THGJFAT0T44BAILB FV=1001 WB=0
(bootloader) ram: 8GB MICRON LP5 DIE=8Gb CH=4
(bootloader) cpu: SM8250 2.1
(bootloader) serialno: ZY22BZBRKZ
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: E2421054
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (2)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-16-2021
(bootloader) sku: XT2125-4
(bootloader) carrier_sku: XT2125-4
(bootloader) battid: SB18C74374
(bootloader) battery-voltage: 3858
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 1
(bootloader) ro.carrier: retcn
(bootloader) ro.build.fingerprint[0]: motorola/nio_retcn/nio:11/RRN31.Q1
(bootloader) ro.build.fingerprint[1]: -20-52-3/2d98f3:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-09000-SMxx50.0
(bootloader) version-baseband[0]: M55_HI20_209.334.01.69R NIO_PVT_SUPERD
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[4]: pr 23 20:53:41 CDT 2021
(bootloader) git:xbl: MBM-3.0-nio_retail-7815c7fde-210503
(bootloader) git:xbl_config: MBM-3.0-nio_retail-7815c7fde-210503
(bootloader) git:abl: MBM-3.0-nio_retail-6b3ddf45a7d-210503
(bootloader) git:aop: MBM-3.0-nio_retail-dca7944-210503
(bootloader) git:tz: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:hyp: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:devcfg: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:cmnlib: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:cmnlib64: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:keymaster: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git:storsec: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git:uefisecapp: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git: prov: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:qupfw: MBM-3.0-nio_retail-e953b4db-210503
(bootloader) git:spss: MBM-3.0-nio_retail-f23af1d-210503
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(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
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93721
(bootloader) primary-display[0]: tianma_nt36672c_1080x2520_670_105hz_dsc
(bootloader) primary-display[1]: _vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.128s
Yasai1204 said:
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Click to expand...
Click to collapse
You really need to unlock the bootloader before trying to change the software channel.
Recovery isn't going to help with this.
You will need fastboot/bootloader mode
Download the RetCN Firmware
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
XT2125-4_NIO_RETCN_11_RRN31.Q1-20-52-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the file
find the flash_file.xml
Open the .XML with a text program like notepad++
Copy the text in the .XML and paste that text to the
Online FlashFile Converter
Use those commands to flash the firmware with fastboot.exe
[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:
You really need to unlock the bootloader before trying to change the software channel.
Recovery isn't going to help with this.
You will need fastboot/bootloader mode
Download the RetCN Firmware
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
XT2125-4_NIO_RETCN_11_RRN31.Q1-20-52-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the file
find the flash_file.xml
Open the .XML with a text program like notepad++
Copy the text in the .XML and paste that text to the
Online FlashFile Converter
Use those commands to flash the firmware with fastboot.exe
[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
Thank you. Will try.
sd_shadow said:
Online FlashFile Converter
Click to expand...
Click to collapse
Hi sorry but in this thread when creating the flashall.bat file, where do I move it to before executing it? The bullet points says: "Move bat file to" before cutting off and the next bullet says "execute bat file by double-clicking on it"
Yasai1204 said:
Hi sorry but in this thread when creating the flashall.bat file, where do I move it to before executing it? The bullet points says: "Move bat file to" before cutting off and the next bullet says "execute bat file by double-clicking on it"
Click to expand...
Click to collapse
Move bat file to the platform-tools folder (adb/fastboot.exe)
Alright, thank you.
sd_shadow said:
Move bat file to the platform-tools folder (adb/fastboot.exe)
Click to expand...
Click to collapse
Thank you so much for your help! My phone has been restored successfully. I honestly thought that I'd bricked the phone and blown my 500 bucks, really should have researched a bit more before attempting this kinda thing. Again, truly thankful for your help!