SPECIAL THANKS
Special Thanks to @Danny XP, @thePromoter, @Hibinoh, and those from the following thread which lead the this thread's inception:
https://forum.xda-developers.com/z2-force/how-to/to-pie-sprint-variant-t3954577
More Special Thanks to the Lineage devs and one of the first real Pie ROMs for the Moto Z2 Force:
Since Morotola decided to not supply a Tmo ROM for Pie on the Tmo variant device, we've only had one good option to go to, Lineage 16. Which, if you like that ROM and want to continue to receive security updates and support, I encourage you to head to this thread and flash LOS 16. The ROM is smooth and works great. Link below:
https://forum.xda-developers.com/z2-force/development/official-lineageos-16-0-t3907036
Please note some current Lineage 16 caveats:
1. Audio routing with Moto Mods does not work. i.e. Gamepad, etc. The Audio HAL is evidently a pain to work with.
2. Efficiency Battery Mode (Allowing the main battery to be charged to 80% from external battery and maintained at that level (Incipio, etc.)) does not work.
The devs on the LOS 16 ROM have done a lot of work and I can't thank them enough for their efforts. They've helped me personally a ton in understanding the Moto Z2 Force and flashing ROMs on Slotted devices, etc.
Why did I move from LOS 16? Honestly, I wanted my Moto Mods working. I got them to enjoy them. If LOS 16 had the audio routing working, I would still be using it. This was my preference only.
Click to expand...
Click to collapse
DISCLAIMER
Back up your files. YOU are responsible for any files that get wiped. The below instructions will wipe your phone.
YOU are responsible if the phone gets bricked. No one else here told you to perform these steps.
I've attempted to make this as simple as I can to follow. Yes, it appears to be a lot of steps. I've tried to avoid assumptions and have done this to help avoid some issues that have been seen when others have attempted to follow the more assumed instructions.
Even with the details below, there will be mistakes. If I've made any, kindly let me know and we can get them corrected.
In no way is this "fool proof" and not every Moto Z2 Force is the same, even the variants can vary within a carrier. So. this is done at your own risk. Please review the instructions before proceeding to ensure you've covered everything before making changes. This was performed on my XT1789-04 Tmo variant.
Even if everything seems perfect, you can still brick your phone.
No one here is responsible in that instance other than yourself. There is plenty of other information here on XDA where you can perform your own research to resolve your issue and decide if you should proceed or not.
Caveat:
1. the ONLY caveat that I've come across is once this is done, Software Updates will not work since your bootloader will be unlocked.
Click to expand...
Click to collapse
Note: In my case, I had to use the "TMO Moto Z2 Force 27.1.5 Flashall" before to prevent boot looping. I was already on Lineage 16 before doing the below. Which was probably the reason why I got a boot loop after flashing all the below files before going back to stock.
More information on the flashall can be found here:
https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
The below should work fine if you are already on stock.
With all that being said, and you feel comfortable, let's get down to it.
INSTRUCTIONS FOR WINDOWS
Quick and dirty
You can follow these if you've already done this before and just want the high-level steps:
1. Download RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest TMO 8.0(XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip)
2. Unzip both files, find a copy of mfastboot (or fastboot), a copy of TWRP img (use nash's TWRP)
3. Copy the boot.img from RETIN 9.0 to your phone's sdcard
4. Boot into TWRP and wipe your phone(data + cache)
5. Copy the below RETIN files to a new folder from the RETIN ZIP file, this is the same folder that the Tmo files will also go:
boot.img
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system_other.img
oem.img
6. Copy the below files from the Tmo ZIP file to the same folder where you placed the RETIN files above:
logo.bin
NON-HLOS.bin
fsg.mbn
BTFM.bin
adspso.bin
7. Copy the twrp<version>.img here as well.
8. Use mfastboot (or fastboot) and flash the files from this new folder with both RETIN and Tmo files that you've copied:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot oem fb_mode_clear
9. Boot into TWRP using mfastboor (or fastboot):
Code:
fastboot boot twrp<version>.img
10. Use TWRP to flash the sdcard copy of boot.img (from step 3) to 'boot'
12. Reboot to finish the install and it should boot for the first time into the new hybrid ROM
13. ENJOY!
More detailed instructions
The reason I posted this was to help prevent some issues with those that have not followed the process before. It should avoid some issues. It is lengthy.
Prerequisites:
1. Unlocking the Booloader
Is your bootloader unlocked? If not, there is no point in doing any of this. If it can't be unlocked, apologies, there isn't anything that can be done from this thread.
Before you go about unlocking the bootloader via the below Motorola website, you need to Unlock the Bootloader witin Developer Tools. To do this, Go to Settings > System > find the Buid Number. Tap the Build Number 8-10 times and it will inform that you are a Developer. Press Back and select developer Tools. Find Unlock the Bootloader, or OEM Bootloader Unlock (You can search for this option.), and tap to enable. Proceed below.
If you need to do this, or find out if it can be unlocked, head to the Motorola "Unlock your Bootloader" site and follow their instructions.
This process WILL VOID your WARRANTY!
Here's the US English link: https://support.motorola.com/us/en/bootloader
1a. Once unlocked, you can continue.
2. Downloading the Files
Below are the files you need in quotes and the links where you can download them from.
If the below won't work you for, search Google for the file names and acquire them otherwise. There were plenty of links the last I searched.
It might be easier if you placed these on your Desktop.
2a. Download ADB Platform Tools, "adb - platform tools v28.0.0.zip":
from https://androidfilehost.com/?fid=962339331459003166
Note: This already has fastboot.exe
2b. Download the 64bit versions of the Motorola Mobile Drivers if you are running a 64bit OS, "Motorola_Mobile_Drivers_64bit.msi.zip":
from https://androidfilehost.com/?fid=23501681358556235
2c. Download the 32bit versions of the Motorola Mobile Drivers if you are running a 32bit OS, "Motorola_Mobile_Drivers_32bit.msi.zip":
from https://androidfilehost.com/?fid=23501681358556234
2d. Download "XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip":
from https://mirrors.lolinet.com/firmware/moto/nash/official/RETIN/
Note: This was tested using RETIN, not RETAIL!
2e. Download "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip":
from https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/
2f. Download "twrp-3.3.1-0-R1-nash.img":
from https://mirrors.lolinet.com/firmware/twrp/nash/
or "twrp-3.2.3-2-nash.img"
from https://dl.twrp.me/nash/
(If you have issues with 3.3.1, use 3.2.3 instead.)
2g. Download fastboot and mfastboot, this link includes both, "Fastboot_all.zip":
from https://androidfilehost.com/?fid=23578570567719065
3. Preparing the Files and Start the Flashing Process
3a. Unzip the files above in their own folders.
3b. Install the Motorola Drivers based on your OS, 32bit or 64bit.
3c. Connect your phone to a USB 2.0 port. You can use USB 3.0, but you might run into issues running commands. If you don't have a USB 2.0 port, perhaps using a USB 2.0 hub might work.
3d. Go into the platform-tools folder.
3e. Run the following to be sure the phone is detected:
Code:
adb devices
You should get some output informing that the ADB daemon isn't running and it will attempt to correct this. Afterwards, you should get something like the following if the phone was found:
Code:
<xxxxxxx> device
If you don't and the command shows that the connection is "unauthorized", change the USB Preferences to File Transfer. Rerun the above command and it should show it as "device".
3f. Using the same platform-tools folder you are running from, copy the following files to the platform-tools folder...
First the RETIN files:
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\boot.img
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.0
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.1
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.2
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.3
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.4
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.5
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.6
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system_other.img
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\oem.img
And, the Tmo files:
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\logo.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\NON-HLOS.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\fsg.mbn
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\BTFM.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\adspso.bin
All of the above files should be within the platform-tools folder.
3g. Copy the XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\boot.img file to your phone's SD Card (Moto Z (2)\SD card). You can use Windows Explorer to do this.
3h. Run the following command to boot into the bootloader (Using either fastboot.exe or mfastboot.exe.):
Code:
adb reboot bootloader
Your phone will reboot and allow fastboot to be used.
3i. Run the following to be sure fastboot detects the phone:
Code:
fastboot devices
3j. Run the following command to boot into TWRP:
Code:
fastboot boot twrp<version>.img
The img file will transfer to the phone and reboot.
Stop here if you have not made a backup of your files or if you have any reservations. This CANNOT be undone!
3k. Select Wipe, select Advanced Wipe, select Internal Storage and Dalivk/ART Cache, and swipe to wipe those partitions.
3l. Tap Back, Back again, select Reboot, and select Bootloader.
You should be back where you can use fastboot.
3m. Use fastboot (or mfastboot) and run the following commands in this order:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot oem fb_mode_clear
Note: I personally only had one file give me an error, that was boot.img. It informed that "verification failed". Continue on step 3n to flash boot.img from the SD card using TWRP.
3n. Boot into TWRP by running the following, as before:
Code:
fastboot boot twrp<version>.img
3o. Select Install, select Install Image, and select boot.img from SD card. When asked, select boot.
Once done, go back to reboot to System to finish the install.
:victory:Voila!!:highfive:
You should now be booting into Pie on your Moto Z2 Force with a hybrid Sprint + Tmo Stock ROM.
If you get a boot loop during the boot animation, as mentioned before, you might need to perform the Flashall to Tmo Stock, and try the above instructions again. I had to.
My build number shows as PPX29.159-24, my IMEI shows up, Android Version shows 9, and all other fields seem to be correct. Voice, Data, and device functions are all working. You are on a mostly-stock ROM now.
Now, the only caveat that I've seen is that when you attempt to check for an update, it will show that the System integrity is compromised. I assume this is because the bootloader is unlocked, etc.
I hope this works out well for you.
Also, if you want root, install Magisk, following this thread:
https://www.xda-developers.com/how-to-install-magisk/
It seems weird that nobody has responded to this. -- Thank you for posting.
---------- Post added at 04:58 AM ---------- Previous post was at 04:40 AM ----------
johnathanamber said:
1. Download RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest TMO 8.0(XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip)
Click to expand...
Click to collapse
Here you're say to use the latest TMO 8.0 firmware; but the the file you're mentioning is not the latest. As per the flashall thread, it says to avoid using the 'August 2019 27.1.7 update and to use the earlier March 2019 Tmobile update.
Is it safe for me to assume that you are intentionally using the 'March update', rather than the 'August update' ?
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-08-05 - August Update (suggested to avoid)
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-03-08 - March update (last stable version?)
Correct me if I'm wrong, but it looks like what you're doing here is using the device specific firmware files from the TMO 'March 2019' update, and then using fastboot to flash the system image from the XT1789-06 (What country / device variant is XT1789-06 btw?) ?
Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried this but it didn't work at all, the phone turns on but it stays in bootloop and I don't know if I did something wrong, I was using the August ROM since the March one was giving me baseband issues
I had an issue with the fastboot oem fb_mode commands (failed: no such file or directory) I'm not sure if this is the problem or not
Is there any way to fix it? Should I try again?
EDIT: I tried again using the flashall and then flashing the rom without letting the phone turn on after using the flashall and it worked
abense said:
It seems weird that nobody has responded to this. -- Thank you for posting.
---------- Post added at 04:58 AM ---------- Previous post was at 04:40 AM ----------
Here you're say to use the latest TMO 8.0 firmware; but the the file you're mentioning is not the latest. As per the flashall thread, it says to avoid using the 'August 2019 27.1.7 update and to use the earlier March 2019 Tmobile update.
Is it safe for me to assume that you are intentionally using the 'March update', rather than the 'August update' ?
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-08-05 - August Update (suggested to avoid)
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-03-08 - March update (last stable version?)
Correct me if I'm wrong, but it looks like what you're doing here is using the device specific firmware files from the TMO 'March 2019' update, and then using fastboot to flash the system image from the XT1789-06 (What country / device variant is XT1789-06 btw?) ?
Click to expand...
Click to collapse
It's possible that I missed the flashall package. I just used what I saw on the aforementioned sites. Apologies for the confusion. You know what, after looking at the quick and dirty vs the full instructions, I had a typo. One shows the XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip file and the other shows XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip. I'll see about updating that.
Thanks for the catch!
gs512 said:
Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
Click to expand...
Click to collapse
Good to note, hope that helps others as well.
DjCreeper7115 said:
I tried this but it didn't work at all, the phone turns on but it stays in bootloop and I don't know if I did something wrong, I was using the August ROM since the March one was giving me baseband issues
I had an issue with the fastboot oem fb_mode commands (failed: no such file or directory) I'm not sure if this is the problem or not
Is there any way to fix it? Should I try again?
EDIT: I tried again using the flashall and then flashing the rom without letting the phone turn on after using the flashall and it worked
Click to expand...
Click to collapse
I, too, had to do the flashall, as noted:
Note: In my case, I had to use the "TMO Moto Z2 Force 27.1.5 Flashall" before to prevent boot looping. I was already on Lineage 16 before doing the below. Which was probably the reason why I got a boot loop after flashing all the below files before going back to stock.
More information on the flashall can be found here:
https://forum.xda-developers.com/z2-...march-t3917070
Click to expand...
Click to collapse
I am glad it worked out.
When doing it this way can you still go back to 8.0 with a flash all if wanted?
jpeeler said:
When doing it this way can you still go back to 8.0 with a flash all if wanted?
Click to expand...
Click to collapse
If you follow the directions precisely then yes.
41rw4lk said:
If you follow the directions precisely then yes.
Click to expand...
Click to collapse
That's what I thought just wanted to be sure. Thanks.
gs512 said:
Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
Click to expand...
Click to collapse
Does this hybrid ROM also remove all the unnecessary sprint apps?
sandner said:
Does this hybrid ROM also remove all the unnecessary sprint apps?
Click to expand...
Click to collapse
Yes
How can I unlock bootloader and install TWRP on my XT1789-04 (AT&T)?
I tried on the website https://motorola-global-portal.custh...-your-device-b but I have received an answer "Your device does not qualify for bootloader unlocking.".
I've been running the T-Mo hybrid on the Sprint hardware (Pie) for a couple of months now (implemented essentially the same way the OP describes).
It mostly works fine, although it has developed an issue where it will frequently freeze and reboot if I try to surf on the phone while I'm on a phone call.
On the reboot, it loops twice before it will reboot.
Also, I am stuck on "H" reception (not LTE) when on a call. Phone is properly provisioned and the settings for T-Mobile are fine and VoLTE is working. But it doesn't see LTE.
I tried doing this but with the Verizon Files, still sees it as a sprint phone. Worse is that it *does* connect to LTE for Data, but not for Voice. Can't make any voice calls at all. Any thoughts?
I finally got around to trying this and have ran into some issues. When I start the individual file flashing I keep getting invalid partition name for each file followed by FAILED (remote failure). Here is an example for the boot file but it does it for all of the retin files from what I can tell.
Sending 'boot__a' (27269 KB) OKAY [ 0.633s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote failure)
Finished. Total time: 0.642s
Sending 'boot__a'
Sending 'boot_a'
Sending 'boota'
try
I have been looking for an update for m sprint Z2 force on stock and this is it! Thank you so much for sharing this!
Looks awesome... I am so happy I don't have to deal with all the sprint junk bloatware on this.
Looking forward to a smooth ride , does anyone have any issue on this?
I,ve managed how to get work Stock Pie on the XT1589-05 RETCN version. HERE is a thread . Thanks to @johnathanamber for idea of hybrid rom
@@johnathanamber @doctorman @dannyxp @thePromoter @Hibinoh
My Sprint stock ROM flashed xt1789-03 has hit the 3G shutdown wall (no VoLTE) on Red Pocket AT&T.
Will following this procedure cure that problem (enable VoLTE plus LTE data)? Bootloader is unlocked already.
Thanks for all your hard work.
Related
Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.
I was on 5.1, bootloader unlocked by sunshine. I rooted to enable tethering, and after did a full unroot. Once the OTA MM update came it couldn't install. Android on back and then rebooted. Instead of trying to fix the software, I decided to get MM from XDA. I flashed TWRP, updated bootloader from computerfreek's thread and flashed his rom for non-verizon.
Now once it turns on I can choose language. At the next page it says select wi-fi netowork, but no wifi networks show up and the Skip button is grayed out.
I followed the directions again and reflashed a few times, but the same result.
I then tried the Brazilian MM from iiwoodstock but with the same result. I flashed his with and without the linked kernal, but again, with the same results.
Any ideas? I was hoping to avoid flashing the stock images, but if that's my only option....
Well I got irritated enough and flashed stock. All is working now.
It was a pain because I only have Windows 10, so RSDLite was being irritating.
Here are the steps I wish someone had put together for me.
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Having ADB Everywhere helps. Just install this:
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Make sure your drivers are installed. I needed to go to motorola to download their software to get fastboot drivers to work:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/103535/p/30,6720,9277
Have a copy of fastboot.exe
(Google it or just do a search on your computer. You probably have a copy of it somewhere if you've ever done anything to a phone)
Here is a link to the .bat file I made that will flash it without needing RSD.
https://nofile.io/f/sh00er98rzM/servicefile.bat
In case someone finds this thread and the file is no longer hosted, here it the text of the .bat file (use Notepad++ or something):
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot erase clogo
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
(Have phone connected in fastboot mode - power plus volume down)
1. Extract the stock image into a folder
2. Put the .bat file in that folder
3. Put a copy of fastboot.exe into the folder as well
4. double click the .bat file
(wait for it to finish. If there's errors, don't worry, it should be fine. Worry when it's worth it. This is not a big deal)
done
I figured this out primarily because of RootJunky.com's youtube video.
https://www.youtube.com/watch?v=njXQYn53SPc
gr8hairy1 said:
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
ChazzMatt said:
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
Click to expand...
Click to collapse
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed
gr8hairy1 said:
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed
Click to expand...
Click to collapse
Release notes here:
https://www.verizonwireless.com/support/droid-turbo-update/
Sent from my carrier unlocked LG V30+ US998
If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.
I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...
What is the reason for relocking the bootloader? You don't get the warranty back...
should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance
Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all
Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?
Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing
I think i did it without flashing the sparsechunk
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the January Patch Stock ROM
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
smyaknti said:
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
Click to expand...
Click to collapse
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
NitrodiumSK said:
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
Click to expand...
Click to collapse
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
smyaknti said:
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
Click to expand...
Click to collapse
Alright gotcha! Thanks a lot for your help
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
No issue downgrade
You can downgrade one power there is no issue of you downgrade it don't worry
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
Any how can anybody provide stock rom oem fastboot mode with March update???
azhar63 said:
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
Click to expand...
Click to collapse
Yeah bro flash this room via fastboot commands
motorola one power
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
aum25 said:
Yeah bro flash this room via fastboot commands
Click to expand...
Click to collapse
Did you flash that rom in 1942- 1 ??? I have the same model num and running oreo... Want to update pie??? Were you successful in doing that ? Because that firmware file was for 1942-2 ? Plz share experience.
rudranshrajput said:
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
Click to expand...
Click to collapse
Did you install any third party app or it happens by itself? I had the same problem but i was messing around with the moto app launcher. Anyhow, try flashing this stock rom with latest june security patch. Don't use TWRP, it is a full rom. Use Fastboot mode. Also backup your device, if you want your files back. This will do a clean install of the rom.
Here is the link: https://drive.google.com/file/d/1lLmDvX4R4o2Jqrhp1RQflap27jxe4hXS/view
Steps:
1) Boot your device into fastboot mode
2) Open flashall.bat and wait for flashing
3) Reboot
colorist said:
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
Click to expand...
Click to collapse
thanks by you my device just boot up in fastboot mod
thank you very much
best regard
Need help with phone bricked.
I was installing the Arrows OS in Motorola one power and after rebooting, the set is in the bricked mode now it's not responding to anything. Can anyone please guide how can I fix it?
I got similar problem.when I'm flashing arrows or others custom ROMs(1custom ROM,2twrp installer)and restart my phone no restarting only bricked.help only blankflash
Phone bricked after installing arrow is on p30 note xt1942-1
I tried the blankflash method but not working, I'm getting I/O error
Any ideas?
I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help.
Look at https://mirrors.lolinet.com/firmware/moto/kiev/official/
Use the file that matches what you have on your phone.
Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?
Kor1134 said:
Thank you for the link. However, my build number [QZKS30.Q4-40-95-9] isn't listed. Should I try QZKS30.Q4-40-95-6?
Click to expand...
Click to collapse
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.
Or just download the 11 to start with
Fandroid Tech said:
build number is not model number. As long as your device is "kiev" you can download any one of the firmware packages.
Click to expand...
Click to collapse
I understand, thank you for clarifying, but all I need is the recovery image. I just didn't want to flash a recovery image with a different build number in the unlikely event there's a difference between my build and whichever build I download. I'd prefer not to flash the whole system if I can avoid it, but whatever, I guess I'll just throw Android 11 in it.
Thx.
So, can someone let me know exactly how to flash the oem images to this phone? I booted into the bootloader and ran the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Now it just boot loops when powering on and entering charging mode.
EDIT: nevermind, I missed super.img_sparsechunk.9, all good now.
XT2113-2
Kor1134 said:
I unlocked the bootloader a few months ago, flashed TWRP and installed Magisk and rooted. Discovered I can't use my work profile while rooted and Google Pay won't work with an unlocked bootloader. So I unrooted and removed Magisk, and locked the bootloader again. Then I got this notification for an OTA update to Android 11, but it fails at step 3 of 6, I assume it's because of TWRP.
I asked Motorola to send me the image(s) necessary for the recovery_a and recovery_b partitions but they refuse to help, despite the fact that as the owner of the device, I also own a license to use every piece of software that comes with it. Can anyone here provide me with the stock recovery image(s)? My phone gives me a notification every 10-20 minutes that this Android 11 update is available and it's incredibly frustrating that I can't get rid of it and Motorola won't give me what I need to fix it.
Thx in advance to anyone willing to help
Click to expand...
Click to collapse
1st. rsdlite, 2nd. fastbootd, 3rd. make back-up(s), 4th. checkout L-os, its a PLETHORA of relevant info ex. dual partition issues and resolutions. AND i do believe
i know this is a bit l8, HOWEVER, in the event it is not too l8 OR you find yourself requiring assistance hmu. ive spent last couple months DARING my kiev to transform into this elusive paperweight...to no avail. along the way ive learn_ed a couple-o-tings, this and the photon q are amazing marvels of techno{imo}
ciao
if anyone has kiev ?s, i MIGHT be albe to help. i am no self professed aficionado or anything but ive been learning about moto's for a few years.
ciao