Database Develop

stock-device bricked itself (battery drained with pinned app, ecnrypted device)

Hi there,
tl;dr:
Basically, my problem seems to be, that any write-operation on my filesytems is refused:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
I found threads about the same problem on Moto G 2013, where "Philz Recovery" was able to fix the partitioning and filesystems, but it seems that this does not exist vor Moto G 2014. And I don't even get any other than stock-recovery working.
TWRP site states: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. " But I could not find any key combo to enter the recovery I just flashed (at least fastboot tells me so) Using "fastboot boot recovery.img" just shows a shortly flickering Motorola-logo every 10 seconds or so.
---
I am having severe issues with my Moto G (2014).
I found some reports of similar issues, but no solution described worked, and it seems I am the only one experiencing this on a stock device.
First some facts:
Device in use since 2 months
Encyption activated about a month ago, no problems
Yesterday, I used screen pinning feature to let my son play a game.
While he was playing, the battery drained until the device shut down.
I connected the device to a charger
After charging 30%, everything first seems normal, I have to enter my encryption PIN and boot process goes on, showing boot animation.
The problem:
At the point, where it would normally finish, the screen just gets black (while still being lit up). Nothing more will happen. The device will remain in this state forever or until the battery is completely drained again.
I first tried using the official methods for (factory) reset described on Motorolas website, they did not work (I am not allowed to post links here yet, google "/prod_answer_detail/a_id/99825/p/30,6720,9151" will show the URL)
Pressing 7-8 seconds restarts the phone, same situation.
Pressing 120 seconds restarts the phone several times, still not working.
I wanted to perform a factory reset, but starting recovery from bootloader only displayed "Boot Up Failed". Choosing "factory" or "bp tools" just started normal boot process. Barcodes seems to work, it shows barcodes.
So next step was unlocking the device to install TWRP. Fastboot displayed no errors, but then not TWRP, but normal recovery starts. Well, better than "Boot Up Failed".
When now performing a factory reset, this is displayed:
Code:
-- Wiping data...
Formatting /data...
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/cache failed
-- Wiping clogo...
Data wipe complete
Obviously, the partitions are untouched (or not there?), and the problem remains.
I also tried to erase cache and userdata using fastboot, there are no error messages, but after rebooting, I am still asked for encryption PIN, so it's basically the same.
I then tried to use adb sideload to flash cm12 nightly. But the device complains that the signature verification failed.
Now, I am not even able to lock the device again, while fastboot states, it would have succeeded.
I wanted to reinstall stock images as described on thetechrism.com (Google: restore-moto-g-2and-generation-2014-stock-lock-bootloader) but I have problems downloading as I only have mobile internet connection at this moment and the download from filefactory stopped two times at 200 MB and I have only about 1 GB traffic for the rest of the month.
I am stuck here, and getting desperate. Did my device brick itself?
I have CM12 and TWRP here, but just cannot get it flashed. This would be my preferred solution, but a reliable source for stock images would also be very nice.
Did anyone experience similar problems when the battery completely drained with a pinned app on an encrypted device?
Thanks in advance for any hint.
Regards
cxxxx

I was now able to download the original firmware.
But...it's the same :'(
I did every step to reinstall stock firmware. No error-messages, neither on console nor on device, everything seems to be fine.
But when I finally reboot, the device again asks for my encryption PIN and will fail to startup!
I still cannot wipe my userdata, still cannot flash a custom recovery...nothing. It's just a ******* brick.
I found one interesting error:
Code:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.066s]
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.133s
How can I manually reformat my partitions in internal storage or how can I force automatically formatting?
Code:
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.041s]
writing 'partition'...
OKAY [ 0.304s]
finished. total time: 0.347s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.134s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.954s]
finished. total time: 1.091s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.134s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.060s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.607s]
finished. total time: 1.075s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 9.899s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 18.063s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 9.860s]
writing 'system'...
OKAY [ 8.230s]
finished. total time: 18.094s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 9.874s]
writing 'system'...
OKAY [ 7.975s]
finished. total time: 17.853s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 8.841s]
writing 'system'...
OKAY [ 7.559s]
finished. total time: 16.402s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.941s]
writing 'modem'...
OKAY [ 0.854s]
finished. total time: 2.798s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot reboot
rebooting...
finished. total time: 0.002s

I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup

izaiasfilho said:
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
Click to expand...
Click to collapse
We are not alone, see here:
http://forum.xda-developers.com/mot...ttery-left-t3085322/post60312526#post60312526
Bad news is, that the problem has not been solved and probably will not as it seems that it's hardware-failure of the flash-storage-(controller).

@cxxxx
I read about it on the moto forums, with users having lost write operations on their phone. And all had one thing in common, they had let the battery die out .
Lesson to be learnt : Never let Li ion batteries totally get drained.
One of the moto moderator told it on their forum to never let your battery totally die. I dont know how much of it rings true as I've let my phone discharged till death many times without any issues.

Same problem here.
After the battery gone once i did't manage to enter. Services errors at android home screen and i can't do recovery - wipe data - cache (all failed). The only thing that i manage is to unlock bootloader.
My question: I 'm thinking to send device for warranty (buying one month ago). Do you think that i 'll have problem with unlock bootloader at service. Somewhere i read that motorola have 2 year warranty for software no matter what. Is that real???

HardBricked unlocked stock lollipop xt1068
Same problem here. But no enconding is on thou.
Can't flash anything - stuck on black screen after boot animation.
XT1068 Unlocked bootloader, stock lollipop, no root, no Motorola service in my country.
Once this devices gone hardbrick, after freaky TWRP could not backup or do anything else. Just could not turn in on at all.
Recovered with jtag riff drivers, but this seems to help bootup, not to flash firmwares - so its not applicable for this case.
RSD Lite 6.1.6 can't see phone, ADB sideload form stock recovery gives no device for adb or windows device manager, but fastboot is okay.
Tryed different computers, different drivers, different stock roms, different fastboot\mfastboot tools, recover scripts.

Hi, guys. I'd face the same problem, but I can boot up, using a Nokia phone charger. Don't know how to explain, but the moto g 2014 charger can't charge enough to boot, when the battery is 0%, then come back to the black screen. With the nokia charger, my moto g boot up normally.
Sorry for my bad english.
Nico

For all those users with soft-bricked "nothing changes after any actions", what if we try to use:
Fastboot erase all
If this would work - bootloader will be dead. We will get the hard brick.
But I have experience of successful recovering xt1068(exactly this one) from hard-brick state, when decice does not turn on at all in any way or mode since bootloader is missing or corrupted.
But PC still can see it over USB cable as QBULC_USB. This one would not work with Motorola drivers nor with any other, but JTAG Riff drivers for QUALCOMM.
Then special low-level tool will load up bootloader.
So? Any suggestions about this?

I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app

Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Click to expand...
Click to collapse
No way of backing up this data?
I remember some of mine old RAZR - I had some backup of unique data for it.
BTW I have the box with IMEI on it, CID saved in notepad, what else...
Stock fw with no root and THIS with no reason.
Also - right before stucked - phone has drained battery from 60% to 0% in pretty short time, then this happened.
Maybe there is some hardware problem with electric circuit..

Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
With my device bricked like this I have tried, CHMOD which has unable to alter the partitions, as well as CHOWN & CHGRP(in both TWRP & ADB), Fastboot erase does nothing along with ADB wipe, TWRP does nothing and no changes can be made as nothing is overwritten, as well as with using Fastboot flash, there have been rumors that Philz can fix it but since nothing can be flashed I cannot try (Unless someone has a way to flash it to SD and let it boot from there, Let me know)
Now with my limited knowledge of android and its partitions and since none of the above methods having any effect I believe that this issue is in fact a hardware one not software related, therefore I think 'Fastboot erase all" will have no effect, that is my opinion gathered from more than two weeks testing, wiping & hoping, if there are any senior users/devs who want to correct me they may, Also if they have any other options I will be glad to try it out.
EDIT: This is purely a hardware fault and no software changes can do anything, I ran Fastboot erase all
...and a reboot later and my device is exactly the same, even boots into recovery fine and fastboot barcodes still shows my original IMEI and Serial number, ADB getvar_cid still also shows the correct CID for my device.
I would upload pictures but I haven't got enough posts to link to tinypic

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

[HELP] XT1069 stuck in fastboot

Hello everyone and sorry for my bad english.
I come here for help with my problem. I bought a Moto G2 TV (XT1069) who was stuck in fastboot mode.
But after more than 40 different procedures in 2 days, nothing worked.
Each command was returned with a failure in the cmd screen.
In fastboot mode no option works except the Barcode option.
My question is: is there a possibility that the main memory has been damaged and fastboot have been saved by being in another memory separately?
I tried everything I found here on XDA and Google and nothing work.
What disturbs me is also the fact of not knowing what version of Android it was, if the bootloader was unlocked or not and if it was with root or not.
CMD Log:
Code:
D:\Downloads\Moto\Android 6>mfastboot flash partition gpt.bin
< waiting for device >
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.008s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.019s
D:\Downloads\Moto\Android 6>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 5.083s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.100s
D:\Downloads\Moto\Android 6>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 5.054s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.081s
D:\Downloads\Moto\Android 6>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 5.357s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.392s
D:\Downloads\Moto\Android 6>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 5.375s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.425s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257435 KB)...
OKAY [ 13.094s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.134s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (255486 KB)...
OKAY [ 13.022s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.066s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (256778 KB)...
OKAY [ 13.080s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.124s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (254001 KB)...
OKAY [ 12.991s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.035s
D:\Downloads\Moto\Android 6>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (50136 KB)...
OKAY [ 6.594s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 11.635s
D:\Downloads\Moto\Android 6>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
D:\Downloads\Moto\Android 6>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.047s
D:\Downloads\Moto\Android 6>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1012 KB)...
OKAY [ 5.100s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.144s
D:\Downloads\Moto\Android 6>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
I accept other suggestions, although I have tried everything I found.

Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty

Hey, can you provide the link to the official android 6.0 thread?
pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse

pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you

ederstk said:
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you
Click to expand...
Click to collapse
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682

pkirtan84 said:
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Click to expand...
Click to collapse
Thank you, pkirtan84! I'll check when I get home and post results!
All the best!

Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!

ederstk said:
Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!
Click to expand...
Click to collapse
um.. what's not working?
download link of Android 6.0 or the process of flashing 6.0?

the flashing process. still stuck in same screen. I try searching more solutions in the web

[URGENT HELP NEEDED] DEVICE WON'T BOOT. please help. please, please!!!

Okay, I had a perfectly working Moto X4 (Indian Retail version), rooted and debloated. But then the idea of going back to unrooted struck me and I flashed the ROM with no problem. Then, I went back to the Bootloader (Had USB Debugging turned on and OEM Unlock "NOT" turned on in the Developer Options) and locked the bootloader by running oem lock and then, the Phone won't boot -
It gave me the message --
" Your Device is Corrupt. It can't be trusted and will not boot."
From then, I've tried reflashing the firmware - No luck.
It gives a "Permission denied" message in cmd and fails.
Unlocking the OEM worked with the get_unlock_data but then it asked me to turn on USB debugging in the developer options (and I can' boot the phone past the message).
I've tried booting into recovery, won't work - just the same message. Tried booting into the bootable TWRP - Won't work. Same message.
Fastboot erase cache erases the cache and won't do anything else.
PLEASE HELP ME. PLEASE....​
The CMD error log reads as -->
Code:
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot devices
ZY224JGPK4 fastboot
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.115s]
finished. total time: 0.123s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bootloader bootloa
der.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.237s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.344s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash modem NON-HLOS.bin
target didn't report max-download-size
sending 'modem' (95999 KB)...
FAILED (command write failed (No error))
finished. total time: 0.010s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash fsg fsg.mbn
target didn't report max-download-size
sending 'fsg' (5508 KB)...
FAILED (command write failed (No error))
finished. total time: 0.008s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bluetooth BTFM.bin
target didn't report max-download-size
sending 'bluetooth' (4540 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash dsp dspso.bin
target didn't report max-download-size
sending 'dsp' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash logo logo.bin
target didn't report max-download-size
sending 'logo' (2153 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_a' (19853 KB)...
OKAY [ 0.438s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.396s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.400s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522692 KB)...
OKAY [ 15.666s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.671s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (521055 KB)...
OKAY [ 15.620s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.626s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523959 KB)...
OKAY [ 15.885s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.893s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (521817 KB)...
OKAY [ 16.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.226s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (522195 KB)...
OKAY [ 16.019s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.026s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524276 KB)...
OKAY [ 16.235s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.242s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (167142 KB)...
OKAY [ 3.634s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.644s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system_b system_ot
her.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.931s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.942s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (237897 KB)...
OKAY [ 5.203s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 5.209s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>

At the time of posting there are only stock images available for the Retail US version of the X4. The only way to get back is to have backed up your original rom and also have "OEM Unlock" enabled in dev settings. Try contacting Lenovo and tell them your issue. They may be able to assist you by providing a stock firmware image or by having you send in your device for service.

Hi, i have just made the exact mistake you did. Did you manage to find a way to fix this?

FIX
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.

I couldn't fix it. And the service center is not providing warranty since I've unlocked the bootloader and they're saying it's irreparable and asking me to change the whole motherboard of a 1 month old handset. I'll be bringing the phone back from service center tomorrow and will be trying this method

bot_rosco said:
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
Click to expand...
Click to collapse
Can you PLEASE FOR the love of God elaborate,please _/|\_

achyut said:
Can you PLEASE FOR the love of God elaborate,please _/|\_
Click to expand...
Click to collapse
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img

bot_rosco said:
Sure,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).

achyut said:
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
Click to expand...
Click to collapse
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck

bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.

bot_rosco said:
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
I can't boot recovery though, shows the same message

achyut said:
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
Click to expand...
Click to collapse
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
achyut said:
I can't boot recovery though, shows the same message
Click to expand...
Click to collapse
i had same, worth a try tho.

bot_rosco said:
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
i had same, worth a try tho.
Click to expand...
Click to collapse
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.

jakejm79 said:
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
Click to expand...
Click to collapse
In think this depends on the firmware as oreo has encryption that does not play nice with twrp so it may not work, worth a try though.

nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails

achyut said:
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
Click to expand...
Click to collapse
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.

bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
QWZR said:
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
Click to expand...
Click to collapse
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command

achyut said:
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
Click to expand...
Click to collapse
You have to download it.
https://androidfilehost.com/?fid=95916177934532795

QWZR said:
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
Click to expand...
Click to collapse
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....

achyut said:
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
Click to expand...
Click to collapse
Have you tried the twrp method that someone mentioned above? Other than that i cant think of anything, sorry.

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.