[Q] XT912 Droid RAZR Bricked after Factory Reset - Motorola Droid RAZR

I have a Droid RAZR XT912 that was working perfectly. I bought it and did a factory wipe inside the phone settings. Rebooted phone only to get stuck at the "Droid" sign. Was running 4.1.2, no rooting ever, and stock recovery. Basically stock everything. So far I've done:
1. Factory Reset In Recovery
2. Matt's Utility Factory Reset to Jelly Bean with Wipe Of Data in Fastboot Mode
3. RSD Lite Flash in Fastboot Mode of version cdma_spyder_9.8.2O-72_VZW-16_1ff.xml
4. Matt's Utility for Factory Reset then the BLUR version of OTA flash in stock recovery.
5. Continuous wiping of data and cache between all of these points.[/B][/B]
Nothing produces anything other than it to freeze at the same point in it's boot. Right at the white lettered "Droid" screen. Please help me! I know it's not hardware because the phone worked find until I factory reset it. Thank you in advance!

RSD Lite Logs for the .165 Flash
Here are my most recent RSD Lite logs for the cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml flash.
07/27/14 10:53:17 Multi upgrade started for 1 phones
07/27/14 10:53:17 [Device ID: 0] 1/24 flash cdt.bin "cdt.bin_signed"
07/27/14 10:53:18 [Device ID: 0] 2/24 reboot-bootloader
07/27/14 10:53:25 [Device ID: 0] 3/24 flash emstorage "emstorage.img"
07/27/14 10:53:27 [Device ID: 0] 4/24 reboot-bootloader
07/27/14 10:53:34 [Device ID: 0] 5/24 flash mbm "allow-mbmloader-flashing-mbm.bin"
07/27/14 10:53:35 [Device ID: 0] 6/24 reboot-bootloader
07/27/14 10:53:41 [Device ID: 0] 7/24 flash mbmloader "mbmloader.bin"
07/27/14 10:53:41 [Device ID: 0] 8/24 flash mbm "mbm.bin"
07/27/14 10:53:42 [Device ID: 0] 9/24 oem fb_mode_set
07/27/14 10:53:43 [Device ID: 0] 10/24 reboot-bootloader
07/27/14 10:53:47 [Device ID: 0] 11/24 flash motoboot "motoboot.img"
07/27/14 10:53:50 [Device ID: 0] 12/24 reboot-bootloader
07/27/14 10:53:57 [Device ID: 0] 13/24 erase cache
07/27/14 10:53:57 [Device ID: 0] 14/24 erase userdata
07/27/14 10:53:59 [Device ID: 0] 15/24 erase userdata
07/27/14 10:54:00 [Device ID: 0] 16/24 flash logo.bin "logo.bin"
07/27/14 10:54:01 [Device ID: 0] 17/24 flash devtree "device_tree.bin"
07/27/14 10:54:02 [Device ID: 0] 18/24 flash system "system.img"
07/27/14 10:55:50 [Device ID: 0] 19/24 flash boot "boot.img"
07/27/14 10:55:54 [Device ID: 0] 20/24 flash recovery "recovery.img"
07/27/14 10:55:57 [Device ID: 0] 21/24 flash cdrom "cdrom"
07/27/14 10:56:35 [Device ID: 0] 22/24 flash preinstall "preinstall.img"
07/27/14 10:58:13 [Device ID: 0] 23/24 flash radio "radio.img"
07/27/14 10:58:18 [Device ID: 0] 24/24 oem fb_mode_clear
07/27/14 10:58:18 [Device ID: 0] reboot

Did you ever get a resolve from these jokers?
Same thing for me, did you ever get a resolve from all these idiots at these forums? I don't see one, but could you remember what you did to get it back or did you trash it? Thanks, I am going nuts trying to figure this out presently.
[email protected] if you could let me know. Thanks.
Speakeasys said:
I have a Droid RAZR XT912 that was working perfectly. I bought it and did a factory wipe inside the phone settings. Rebooted phone only to get stuck at the "Droid" sign. Was running 4.1.2, no rooting ever, and stock recovery. Basically stock everything. So far I've done:
1. Factory Reset In Recovery
2. Matt's Utility Factory Reset to Jelly Bean with Wipe Of Data in Fastboot Mode
3. RSD Lite Flash in Fastboot Mode of version cdma_spyder_9.8.2O-72_VZW-16_1ff.xml
4. Matt's Utility for Factory Reset then the BLUR version of OTA flash in stock recovery.
5. Continuous wiping of data and cache between all of these points.[/B][/B]
Nothing produces anything other than it to freeze at the same point in it's boot. Right at the white lettered "Droid" screen. Please help me! I know it's not hardware because the phone worked find until I factory reset it. Thank you in advance!
Click to expand...
Click to collapse

Related

Can't boot. Can't load stock 173 or 181

Well I tried the ICS update at:
http://forum.xda-developers.com/showthread.php?t=1599234
But I never got past step 1...reverting to a stock 173.
It fails on the system writing step...and by fails I mean I got tired of waiting after 20 minutes.
I tried the RSD Lite 5.6 method with the included files:
Blur_Version.6.12.173.XT912.Verizon.en.US.zip
Blur_Version.6.12.181.XT912.Verizon.en.US.zip
But all it says is damaged/missing an xml file.
So I tired the 173/181 files from sbf.droid-developers.org
VRZ_XT912_6.5.1-167_DHD-14_M2-5_CFC_1FF_01.xml.zip
VRZ_XT912_6.5.1-167_DHD-14_M3-8_CFC_1FF_01.xml.zip
They reported an error code regarding OEM commands.
Guide at droidrzr.com called "1107-fix-unknown-fastboot-command-oem-phone-connected/" said remove the OEM codes...so I did....
But still on 173/181 system.img takes over 20 minutes.......am I not waiting long enough or...
I have no idea.
Trying the image VRZ_XT912_6.5.1-73_DHD-11_M1-2_1FF_01.xml.zip instead right now.
I didn't have to remove the OEM code...maybe that's a good sign?
I think I figured out why the BLUR ones don't work...they are OTA updates.
.......
I wrote a batch script from the xml file.
For paranoia's sake I put a reboot after every command.
It doesn't work though...it still gets stuck on the system.img step.
it's been stuck on the system.img step for 35 minutes now.
moto-fastboot.exe flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash mbmloader mbmloader.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash mbm mbm.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash cdt.bin cdt.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe erase cache
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe erase userdata
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe erase emstorage
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash logo.bin logo.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash ebr ebr
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash mbr mbr
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash devtree device_tree.bin
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash system system.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash boot boot.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash recovery recovery.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash cdrom cdrom
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash preinstall preinstall.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash emstorage emstorage.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash webtop grfs.img
moto-fastboot.exe reboot-bootloader
moto-fastboot.exe flash radio radio.img
moto-fastboot.exe reboot-bootloader

moto-e with stock ROM - bootloader says "Software Status: Modified"

Hello, I have a motoE 2 LTE (XT1514 Surnia) that originally had Android 5.0.2, but it went to motorola for repair and came back with 6.0. Despite the upgrade, the bootloader screen still showed "software status: official".
The I have unlocked the bootloader, installed TRWP and used it to flash supersu. The log says the process was successful but I checked with the app root checker that it was not.
Then I wanted to go back with the stock ROM. I downloaded the XT1514_SURNIA_RETBR_DS_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml ROM from this link I found on xda-developers and flashed it with RSD Lite. The system works but the bootloader screen now says "software status: modified"; before this process I made a backup using TWRP but after restoring the bakcup image the message still didn't change back to "software status: official".
I thought maybe I need to install the original Android (5.02) and then upgrade it to 6.0, so I downloaded the XT1514_SURNIA_RETBR_DS_5.0.2_LXI22.50-53.8_cid12_subsidy-DEFAULT_CFC.xml ROM from the same link. The problem is I get a failure message when I try to flash the 5.0.2 image
Code:
# mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.125s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.570s
I did try with RSD Lite too, but I get the same message. I've read somewhere you can't dowgrade stock firmware, is the the problem here ? There is any workaround ?
My final objective is to have stock firmware with android 6.0 installed and the bootloader message saying it is official. I appreciate any help =)
ps. Even after flasingh the stock ROM there still a folder called supersu on the root folder. How is this possible ?
This is the log of RSD Lite flashing the stock image with android 6.0
Code:
28/16 05:39:10 The FlashLog key is turned off.
09/28/16 05:39:10 Multi upgrade started for 1 phones
09/28/16 05:39:10 [Device ID: 0] 1/20 getvar max-sparse-size
09/28/16 05:39:10 [Device ID: 0] 2/20 oem fb_mode_set
09/28/16 05:39:10 [Device ID: 0] 3/20 flash partition "gpt.bin"
09/28/16 05:39:11 [Device ID: 0] 4/20 flash bootloader "bootloader.img"
09/28/16 05:39:12 [Device ID: 0] 5/20 flash logo "logo.bin"
09/28/16 05:39:12 [Device ID: 0] 6/20 flash boot "boot.img"
09/28/16 05:39:15 [Device ID: 0] 7/20 flash recovery "recovery.img"
09/28/16 05:39:18 [Device ID: 0] 8/20 flash system "system.img_sparsechunk.0"
09/28/16 05:39:42 [Device ID: 0] 9/20 flash system "system.img_sparsechunk.1"
09/28/16 05:40:03 [Device ID: 0] 10/20 flash system "system.img_sparsechunk.2"
09/28/16 05:40:22 [Device ID: 0] 11/20 flash system "system.img_sparsechunk.3"
09/28/16 05:40:42 [Device ID: 0] 12/20 flash system "system.img_sparsechunk.4"
09/28/16 05:40:49 [Device ID: 0] 13/20 flash modem "NON-HLOS.bin"
09/28/16 05:40:54 [Device ID: 0] 14/20 erase modemst1
09/28/16 05:40:54 [Device ID: 0] 15/20 erase modemst2
09/28/16 05:40:54 [Device ID: 0] 16/20 flash fsg "fsg.mbn"
09/28/16 05:40:54 [Device ID: 0] 17/20 erase carrier
09/28/16 05:40:55 [Device ID: 0] 18/20 erase cache
09/28/16 05:40:55 [Device ID: 0] 19/20 erase userdata
09/28/16 05:40:57 [Device ID: 0] 20/20 oem fb_mode_clear
09/28/16 05:40:57 [Device ID: 0] reboot
09/28/16 05:40:57 CMultiFlashFlex::RebootPhone, waiting for phone to disconnect, status=2, state=0.
09/28/16 05:40:58 Removal, interface=28(0x0), device id=1636460.
09/28/16 05:40:58 CMultiFlashFlex::RebootPhone, waiting for phone to connect, status=3, state=4.
09/28/16 05:48:08 00002de8 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
09/28/16 05:48:08 CMultiFlashFlex::RebootPhone, unable to wait for phone, status=3, state=4.
09/28/16 05:48:08 [Device ID: 0] Please manually power up this phone.
09/28/16 05:55:18 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1
09/28/16 05:55:18 [Device ID: 0] Please manually power up this phone.
09/28/16 06:02:28 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2
09/28/16 06:02:28 [Device ID: 0] Please manually power up this phone.
09/28/16 06:08:36 Arrival, interface=36(0x0), device id=1636460.
09/28/16 06:08:36 [Device ID: 0] Waiting for others to finish current operation.
09/28/16 06:08:36 Arrival, interface=20(0x0), device id=1636460.
09/28/16 06:08:36 Arrival, interface=19(0x0), device id=1636460.
09/28/16 06:08:36 The FlashLog key is turned off.
09/28/16 06:08:36 FlashLog file is turned off.
09/28/16 06:08:36 Multi upgrade finished.
you can install the stock mm firmware without any issues, but cant keep the status as official. Coz ive flashed the firmware multiple times and have had the status to be modified and not official.
ASKdroid said:
you can install the stock mm firmware without any issues, but cant keep the status as official. Coz ive flashed the firmware multiple times and have had the status to be modified and not official.
Click to expand...
Click to collapse
Hi, ASKdroid, thanks for answering, I thought this might be how it works, but I've seem videos of people rainstalling stock and the message did change back to official. Check this one at times 1:10 and 11:20

[GUIDE] How to correctly flash a GSI rom and avoid fastboot boot bug

Disclaimer:
use this guide at your own risk. Flashing it may brick your device. I'm not responsible for any software/hardware and any kind of damages/losses.
GUIDE​
Download your rom (i suggest you omnirom or RR remix).
Download this files (MANDATORY)
Download TWRP
vbmeta
Reboot to fastboot, and do all of this in one time (don't reboot to one to another command).
-fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
-fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
-fastboot erase system_a
-fastboot erase system_b
-fastboot flash system_a nameoftherom.img
-fastboot flash system_b nameoftherom.img
-fastboot reboot
-press again the volume - + power to re enter in bootloader
-fastboot getvar all, see what partition is active
-fastboot --set-active=_a if the active partition is _a or _b if the active partition is _b
-fastboot boot twrp.img
-Once booted, go to wipe, and swipe to wipe data\factory reset.
-Go to wipe again, advanced wipe, tap on system squarebox, select Repair or Change File System, tap on resize file system then swipe (this will allow you to flash gapps)
-Flash Gapps
-Flash magisk
-Flash Twrp permanent link
Enjoy!
Sir i can't flash gsi image bigger than 2.5gb..
Any solution for this???
Because many popular gsi rom size is over than 2.5 gb..
Pixel Dust GSI
Is there any way to manually update security patches on this ROM?
brtq82 said:
Is there any way to manually update security patches on this ROM?
Click to expand...
Click to collapse
You have to flash the newest version of the GSI manually.
I've tried several GSI roms, and I can't select LTE on any of them, only the global option, so when I select my apn I can't make or receive calls? Anybody know the solution for this?
There is a small mistake in your guide.
The line
Code:
fastboot --set-active=_a
should be
Code:
fastboot --set-active=a
The underscore in your line made me not able to switch slots and when I removed the underscore it worked!

[HELP] G7 power permission denied

Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
pacomiguel said:
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
sd_shadow said:
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hello, thanks for the information but I had tried to do that before, the bootloader is locked on my device and there is no way to unlock it in the condition that my cell phone is.

Android One - 10 Update Retail

Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmware/moto/deen/official/RETAIL
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
ALSO YOU CAN USE RSD Lite Tool
Please
I Don't know to Re-Lock Boot loader. It shows Need signed Bootloader
can be installed in phone version? is there any risk?
Enviado desde mi Pixel 2 XL mediante Tapatalk
I flashed it and it works pretty good.
I havent had any issues.
Unique code
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
cyyy said:
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
Click to expand...
Click to collapse
Ok! I'll try another time!
deveshbabu said:
Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Justphemy said:
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I'm using the Lenovo Moto Smart Assistant PC application and I'm in the middle of the upgrade.
FaBMak said:
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
Click to expand...
Click to collapse
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Justphemy said:
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Click to expand...
Click to collapse
I don't know, i just saw this on the other thread. I think that if it's working ok, keep it.
if my device is RETLA will RETAIL work fine on it?
EDIT: I can confirm, as of first boot, everything seems to be in order! functioning LTE, anyway!
EDIT2: Play store is broken, everything gets stuck at 99%. going to try to rollback to Android 9.
Also I need help locking the bootloader on Motorola one p30 play xt1941-3 please help anyone.

Categories

Resources