Related
Okay, guys...
I have a big, big, big issue and If it's possible, I'd like all the help in the world.
I unlocked my bootloader, upgraded to mm 6.0 and decided to root and install TWRP because bloatware, right?
Anyways, I did a big no-no and after a series of unfortunate events, I don't have a recovery and I can only boot into the bootloader.
Don't ask HOW I got here, I couldn't tell you with a gun to my forehead.
Now, I have tried ways to get myself out of this:
Installed an earlier TWRP recovery - doesn't work
Installed CM recovery - Doesn't work
Looked on motorola.ca for stock images - doesn't work
I can boot my phone with TWRP but I can't install it. (the inapropriate partition size error in pink)
whatever. Whenever I boot into twrp, I see all my partitions and with modifications on, I cannot format my /sdcard/ partition (internal memory)
it was being detected by my pc a few times and after a few more tries to flash ANY rom compatible with my phone, I simply have no luck.
Any advice right now is more than appreciated!
Awaiting answers with impatience.
EDIT: Forgot to mention the model number is the XT1097 canadian Moto X 2014 (Telus mobility)
Thanks for the help in advance
Have you tried this? Put ROM/gapps on internal storage. Fastboot boot twrp, then flash ROM/gapps with twrp. Once booted you should be able to install twrp via playstore without the partition mismatch issue. I had to go this route to get twrp to stick on my XT1096
I cannot access the internal memory for some reason!
I hear my pc make a sound for connected but it doesn't show up in explorer
Have you tried ADB sideload? Try flashing the stock MM Rom Zip located in the Moto X 2014 XDA Thread. It might work, if it doesn't, I can send you a toolkit that might fix the phone.
I did try to sideload and I get the following:
Installation failed: unable to mount (all the partitions are listed)
E: Failed to mount
E: Can't mount
And if you're talking about RDS Lite, I am completely unable to find my phone with it.
What I really need is a tool that will fix the partition table.
I don't know how, but I messed it up REAL GOOD!
also, for some reason I Have 2 recoveries atm.
When I completely power off my phone and then power on, I boot into the CyanogenMod Recovery.
THEN, when I reboot into recovery, I go into the TWRP recovery.
And every time afterwards I Reboot to recovery, I come back to the TWRP
Install Motorola USB Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download and keep full firmware VICTARA_RETCA_XT1097_6.0
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
If you are able to flash with fastboot, maybe you can go back to stock, then go on from there.
Try these, one by one:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
I know you wouldn't, but hope you do. But if you could tell me how you got here, I could assist you better.
Thank you, Mate!
This restored my phone to retail!
I am in your debt!
You're welcome. We are all here to help each other.
Hi, I am in the exact same situation right now. I tried the fastboot method to flash all the files for the XT1096 VZW version. Every time I boot up after flashing everything, the dead andy with read exclamation point 'No Command' logo pops up and blinks every 5 seconds or so. Any help please? Thanks!
So I managed to get TWRP to install. Now I can't flash anything. All the partitions are somehow corrupted and I can't mount anything. Any ideas on how to fix the partitions?
OK
My apologies, Gus. I just posted a new QA thread on here. Can we discuss there? Thanks.
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Speedy712 said:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Click to expand...
Click to collapse
So you have the Motorola USB drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Recent versions of ADB/Fastboot.
Latest stock firmware:
firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1096/
Probably VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Extract the firmware and put the 4 ADB/Fastboot files in the folder with the firmware files.
Boot into Bootloader Mode and connect the phone, make sure the phone says "connected..."
Shift + right-click inside that folder, Open command window here... Paste these commands, BUT CHECK THE NUMBER of sparsechunks your firmware has:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Speedy712 said:
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Click to expand...
Click to collapse
You're welcome, glad it worked!
If you want to try custom roms again, I've been using TWRP 3.0.2-1 and it seems to have no issues so far (and I'm running the latest CM Nightlies).
Gus Ghanem said:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
so with this method you dont have to use the motofastboot?
fakieskr8333 said:
so with this method you dont have to use the motofastboot?
Click to expand...
Click to collapse
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Gus Ghanem said:
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Click to expand...
Click to collapse
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
fakieskr8333 said:
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
Click to expand...
Click to collapse
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Gus Ghanem said:
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Click to expand...
Click to collapse
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
fakieskr8333 said:
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
Click to expand...
Click to collapse
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Gus Ghanem said:
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Click to expand...
Click to collapse
Thanks, I am at work now but as soon as I get home I will give it a go. I have been on iOS for over a year now and my moto has been dead since about a month after moto allowed us to unlock the verizon variant. Stupid thing lol.
how do I check the amount of sparsechunks that I have. Sorry for the dumb question
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
I just finished doing this. I am kind of a noob at this so bear with me. I tried this and I get this message that says "Boot up failed" when I try normal powerup. I'm kind of scared..
ABSOLUTE LEGEND
i was stuck since almost 36 hours, good i dint lose hope and smash the x against the wall
YOUR A LIFE SAVER Fakieskr
As the title says, I have no recovery and can't seem to restore the stock recovery. Also, when I boot/reboot the phone, it goes to fastboot mode. Then if I select START, it will boot to the system.
I purchased this phone used and the bootloader was already unlocked. I installed TWRP, rooted it and set it up. When I put my sim in, I could send & receive text messages and mms messages, but I was unable to talk or hear anything while on a voice call. The call is placed and/or received fine. However, once connected, I cannot hear anything nor can anyone hear me.
I want to return for a refund and have restored to factory per this guide. (the problem persists). However, I do not have a recovery. Flashing the stock recovery thru ADB appears to work but trying to boot to it goes to fastboot mode. I cannot boot/reboot the phone without it going to fastboot, then I have to select START to boot to the system. If I cannot correct these problems I will not be able to return the phone...and I can't use it as is because of the phone issue.
Thanks...and help!
Did the phone work fine when you got it?
Sent from my Moto G6 Plus using Tapatalk
Relock-it
Remember you need root to do this and usb-debugging and OEM-unlock enabled in syste settings
Download firmware ALI_RETAIL_8.0.0_OPS27.104-15-10-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
and assuming you know were to extract it to, run this command:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot and run this command ONE BY ONE and wait for each one to finish before adding the next one
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear
Xplorer4x4 said:
Did the phone work fine when you got it?
Click to expand...
Click to collapse
Booting up and recovery...yes.
xjunior said:
RELOCK IT
Click to expand...
Click to collapse
What will that do for me? I still don't have a recovery.
xjunior said:
wen it finish the process DO NOT PRESS ENTER erase fastboot reboot
Click to expand...
Click to collapse
I don't understand this. How do I erase fastboot reboot? It's a command to reboot.
if you use the firmware from the guide you show in the first post is probably not the right one for your device, I have exactly same model and took me a wile to figure out how to factory reset and relock it.
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command, line by line not all at once like the first part.
this will bring you device back to factory and relock the bootloader ,
xjunior said:
yes you gonna put the first commands all at once ,
then in the cmd terminal its gonna be the last command "fastboot reboot" but do not press enter otherwise it will reboot,
erase it and
add the second part of the command line by line .
this will bring you device back to factory and relock the bootloader ,
Click to expand...
Click to collapse
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
mn1968 said:
OK. Understood. But how will relocking the bootloader help me? It reboots to fastboot...it doesn't reboot to the system/OS. What I need is a recovery to somehow be flashed and to "stick".
Click to expand...
Click to collapse
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
xjunior said:
the last command will fix that I had same problem.
if you fallow this guide.
fastboot oem fb_mode_clear
If you want to return the Phone you will need to relock the bootloader other wise they will blame you for messing up the phone.
Click to expand...
Click to collapse
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
My pleasure
mn1968 said:
OK, with your help I am back in business! I actually re-followed this guide up to step 5. I then ran:
fastboot oem fb_mode_clear
I can have the phone reboot normally now! Thank you very much!!!
As far as returning, I got it used on eBay. The bootloader was already unlocked. It's the phone that doesn't work for actual calls. I just need/wanted to return it exactly like it was.
Thanks again for your help!
Click to expand...
Click to collapse
After reflashing stock with OPS27.82-72 (came with OPS27.82-19-4), the phone now actually works too. Very weird. I may have/want to keep the phone now.
Hi there, my device was having boot loop problems, I followed this guide using files uploaded by a user, then I was able to update using otg cable but it got stuck at 25%, after a reboot I get the message that my device is corrupt and cannot be trusted.
This is the guide i followed :
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
Now I have tried to flash at fastboot the following images:
En_wpj0O_v115
En_wpj0O_v207
En_wpj0O_v209
En_wpj0O_v210
Chinese 2.31
I used the following commands each time:
fastboot oem nubia_unlock NUBIA_NX629J
Fastboot erase boot
Fastboot erase recovery
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
Fastboot erase data
fastboot erase system
fastboot erase modem
fastboot erase dsp
fastboot erase vbmeta
fastboot erase dtbo
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash dtbo dtbo.img
fastboot flash dsp dspso.bin
fastboot flash vbmeta vbmeta.img
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
Each time I've tried I just end up with the device is corrupt message, I have read that the command 'Fastboot flashing unlock' can solve the problem but when I enter it I get an error message that it's not allowed.
I would really appreciate some help getting this back up and running, maybe I'm doing something wrong or not using the correct images but I'm now at a loss.
Also my battery is now getting low which is worrying me.
Many thanks,
John.
Edit also followed this:
https://forum.xda-developers.com/red-magic-3/how-to/stuck-fastboot-mode-check-ub-debugging-t3951498
I used the files from global 2.31 and system.img uploaded by a user in that thread.
Then the following commands:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash -S 500M system system.img **I have to do it this way else it fails**
fastboot reboot
Unfortunately I still get the device is corrupt and cannot be trusted message. I am really stuck now
One thing I have noticed is when I flash system.img although it completes with all ok messages I cannot send any fastboot commands after doing this although fastboot devices shows the phone.
Should also mention that I cannot enter recovery from fastboot, just get the corrupt message.
Success.
I had to do:
fastboot flash -S 100M system system.img
Sending in larger chunks must have corrupted the image, I'm now back at the recovery and hopefully can go from here.
Update
Flashed latest EU rom over otg after clearing data and cache, all working.
What a relief!
Red magic 3 software crupt
My friend I'm facing same problem
I can't go to the recovery to restore flash file from usb OTG
Also fastboot is not allowed to unlock flash
How can i get back ok my device?
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