Database Develop

i think i bricked my moto- please help me decide

the first question:
From fastboot, (or mfastboot,) I'm attempting to write and reflash my system. Would cyanogen mod have named the partitions anything other than what they are?
(example of command i attempted : mfastboot format system
Mfastboot replied something about variables, and system not being one of them)
Can someone tell me how to get a sort of cm11 device map, or diagram with all partitions and file path names?
So how did i get here?
I was running low on storage and decided to stop by my buddies place to use his pc and clear some space in my device. (recently unemployed, evicted, completely screwed, yea- REALLY.) Quickly after i plugged into the pc i had to unplug for a moment so i just pulled the usb cable from the port, like i have done many times before, bypassing the pc's directions to disconnect first... Immediately my phone started boot-looping only the "bootloader unlocked" screen over and over... The first thing i attempted to remedy the situation was hold the power button for 10 seconds in an attempt to restart the device. When it began doing things the same way, i went to recovery, via fastboot, and attempted to 'install zip from sdcard'. The reply was that recovery couldn't mount storage. I tried to reboot recovery and try again but got the same result. Next i rebooted to recovery and attempted to factory reset but it froze recovery after i confirmed the command. Had to hold power + volume down for 10 seconds and let it reboot to fastboot, choose recovery, then mounts/storage, format system, and that froze recovery again, so, now I'm realizing that recovery is broken.
I hooked up top the pc and went to fastboot mode, made sure my device was recognized, then read up on some commands, because, honestly, I've rarely used it outside of doing strictly what some tutorials told me to do. (Although, the last time i had to use it, i had great success using minimal reference and mostly luck, i saved my moto x from what i thought was certain death.)
Unfortunately, this time, I'm pretty certain. But at the same time- i can get to recovery, that's a great sign, right? To me, it means it's not dead yet!
First i used fastboot in an attempt to format the caché, just to 'feel it out.' I wish i could remember what it told me, but the gist of it sums up to the cache being erased, but the rest if the reply was negative.
I tried similar commands from formatting the system to the recovery in order to rewrite the recovery image, but no luck there... All commands give me responses regarding variables or they are bring denied by the device, which brings my next question, (which is not a cm question, but a general one... I only ask here because i began this post with a question regarding cm)
When a moto x with an unlocked bootloader boots to AP fastboot, at the end of the first line at the top there is
(S)
I believe on my past rooted devices that either (S-ON) or (S-OFF) would be there regarding their status as superuser.
With my device displaying only ' (S) ' in this place, does that indicate that I've lost superuser privileges our anything at all, for that matter?
I am so lost, friends... That device is everything to me, even without cellular service, when i get close to wifi, i contact my family, look for a job, read, and keep up with my medical requirements.
As i live to say at this point, any and all info and input will be greatly appreciated!!!

If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk

Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
That's such good news! I'm not familiar with rsd, though. What is it all about? And no, I didn't try stock firmware...

Here's the solution.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Thanks to @TechSavvy2 for his guide.
Enviado desde mi XT1053 mediante Tapatalk

Have you tried mfastboot or fastboot erase instead of format?

Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).

samwathegreat said:
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).
Click to expand...
Click to collapse
Thanks! I am helping because I bricked my phone recently and I don't want that people do the same. I can't write too much (yet). My main language is Spanish and I'm just an English trainer. Greetings!
Enviado desde mi XT1053 mediante Tapatalk

Help with Bootloader.

Morning everyone. I'm having some troubling problems with my bootloader. I've had it soft bricked before and was fairly easy to fix. But something is drastically different now. It seems every time I try to restore one of my saved backups, it freezes after a certain point, and sends me back in the boot loader loop. Every time I try to wipe system/data/cache it freezes and back to the bootloader loop. I tried opening a command prompt in adb, but it just says device isn't connected. I can still get into twrp and into the bootloader selection modes. It's just when I do certain things it freezes. For my backup I was able to get it to 36% completed before it froze. My phone is a Moto X 2nd Gen xt1097, and I am running a nightly CyanogenMod on it. Updated it last time about 2 days ago. I just cant find anything on how to fix this. Any help will be much appreciated!! Thanks!

Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?

USA1791 said:
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
Click to expand...
Click to collapse
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?

Gus Ghanem said:
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Click to expand...
Click to collapse
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.

USA1791 said:
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
Click to expand...
Click to collapse
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have

Gus Ghanem said:
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Click to expand...
Click to collapse
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.

USA1791 said:
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
Click to expand...
Click to collapse
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.

Gus Ghanem said:
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Click to expand...
Click to collapse
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?

USA1791 said:
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
Click to expand...
Click to collapse
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?

Gus Ghanem said:
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Click to expand...
Click to collapse
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.

USA1791 said:
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
Click to expand...
Click to collapse
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working

Gus Ghanem said:
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Click to expand...
Click to collapse
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.

USA1791 said:
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
Click to expand...
Click to collapse
Yes it looks like fastboot is working, you should delete those screenshots now.

Gus Ghanem said:
Yes it looks like fastboot is working, you should delete those screenshots now.
Click to expand...
Click to collapse
Oh. Okay got them deleted. Didnt think they'd show anything personal?

After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 0 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
USA1791 said:
Oh. Okay got them deleted. Didnt think they'd show anything personal?
Click to expand...
Click to collapse
Sort of, unique to your own phone, like IEMI, Serial Number, etc.

Gus Ghanem said:
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 9 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Click to expand...
Click to collapse
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!

USA1791 said:
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
Click to expand...
Click to collapse
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2

New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?

Gus Ghanem said:
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
Click to expand...
Click to collapse
Oh thanks, I guess they are dated lol.

USA1791 said:
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Click to expand...
Click to collapse
No don't flash supersu, it causes problems
Yes try copying the CM and Gapps zips to you phone, and try flashing them with TWRP...
which version TWRP you have on the phone?

Booting TWRP through fastboot doesn't work

Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.

ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?

gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf

Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?

Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..

Are you using minimal or full sdk (by Google) platform tools?

Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.

I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.

Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha

I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.

https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.

No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.

Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.

Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?

Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird

A different pc solved the issue.. wtf.. thank you..

I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.

dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..

[Pro Help Needed with restoring phone to factory settings]

Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.

e4noob said:
Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
Click to expand...
Click to collapse
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.

madbat99 said:
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
Click to expand...
Click to collapse
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.

e4noob said:
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
Click to expand...
Click to collapse
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!

madbat99 said:
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
Click to expand...
Click to collapse
Thanks. That helps a lot.

e4noob said:
Thanks. That helps a lot.
Click to expand...
Click to collapse
Good luck!

madbat99 said:
Good luck!
Click to expand...
Click to collapse
Again, appreciate the help a lot.
So I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas?

madbat99 said:
Good luck!
Click to expand...
Click to collapse
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )

e4noob said:
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
Click to expand...
Click to collapse
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.

madbat99 said:
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
Click to expand...
Click to collapse
Yes the same version. I have it on fastboot when connecting (also tried normal bootup and pc recognizes phone just fine). Good to know there is the bat file option for last resort. I'll try installing android sdk and may be it'll solve this driver issue. So I'll have to ask you for the steps to make the the bat file and how to make it work.

You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.

Ragarianok said:
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Click to expand...
Click to collapse
What does it do and how do you use it?

e4noob said:
What does it do and how do you use it?
Click to expand...
Click to collapse
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.

Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
I'm gonna try it out if it works for moto g6. Thanks, man.

Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?

e4noob said:
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
Click to expand...
Click to collapse
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.

Ragarianok said:
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Click to expand...
Click to collapse
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?

e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Yup! That's completely normal.

e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Do you really need it locked?

Ragarianok said:
Yup! That's completely normal.
Click to expand...
Click to collapse
I'm getting this message.
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.010s]
finished. total time: 0.011s

Question Straight forward way to unbrick Redmi note 10 pro global version!

My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?

Robbie D said:
My device is bricked coming from a custom ROM in this forum.. I'm not gonna bash the ROM or developer... The thing installs its own custom recovery. I tried to switch ROMs, but could not. Somehow I have managed to brick my phone to the point that it only boots into fast boot mode. I've seen several little guides and snippets here and there but none are truly direct and to the point of how to recover the phone back to stock. I'm not a developer nor do I know how to use command prompt or powershell or linux. I can use the mi flash tool, but always get error missing install.bat?
Click to expand...
Click to collapse
I would suggest side loading TWRP via adb in fastboot, at least you'll get recover back and can start from there.

I have tried to do that.. for some reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
edit : grammar.. using cheap phone till I can get my sweet restored and working again.

Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?

Robbie D said:
I have tried to do that.. for dinner reason it doesn't work. I've tried several methods exactly as suggested. They always fail..
Click to expand...
Click to collapse
Further to what I said above, try this method

Xavind said:
When in fastboot mode and connected via the USB cable, in command prompt when you type "fastboot devices" and press enter does your device show up?
Click to expand...
Click to collapse
no.. nothing happens

Robbie D said:
no.. nothing happens
Click to expand...
Click to collapse

Adb should be in root path c
It should be started with admin rights and of course the drivers for the phone should be installed before

I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..

Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
Xiaomi Redmi Note 10 Pro USB Drivers | Device Drivers
The drivers to connect/unlock the Xiaomi Redmi Note 10 Pro smart phone to backup,tether, network and more are below. Be aware if you are looking to unlock the bootloader or other advanced software functions it most likely will void any existing warranty. Also Functions used at the fastboot...
oemdrivers.com

Robbie D said:
I can do that tomorrow...I spent 6 hours effen with it today and pretty frustrated..
Click to expand...
Click to collapse
update drivers , then pc should read fastboot.
download and then flash recovery using
fastboot flash recovery (***).img
through recovery install rom again

I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though

Finally got back to this and made sure to put all of the files in c: drive... It shows something on a port, but no devices..

I connected my cheap moto g play and it shows up. I guess that eliminates bad cable and possibly phone is literally Perma bricked?

Xavind said:
I hope you watched the video I added to the thread. Launch command prompt in the folder you have adb in. Drivers are key though
Click to expand...
Click to collapse
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.

Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?

Robbie D said:
I did watch it several times. I was doing everything you did, step by step... Had to pause,rewind, etc... Several times. The only step you didn't really specify was putting it all on c:\drive... Very helpful video and much appreciated.
Click to expand...
Click to collapse
Did you solved it now or not?
Which drivers you've installed?

No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.

Robbie D said:
No.. Still bricked! I installed the driver's that were linked in the video and I had them installed from when it was working properly.. Drivers aren't the issue.. I'm not sure what to try next.
Click to expand...
Click to collapse
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices

Laptapper said:
Try to connect the phone again
If Adb fastboot devices not working then leave phone connected and restart the phone to fastboot again via phone buttons and if restarted fastboot mode try again to adb fastboot devices
Click to expand...
Click to collapse
Did you look at the photos in my previous 2 posts? The first shows something is there, but doesn't give a device name or number.. The 2nd shows my moto g play and it is identified by fastboot devices... I think the entire storage, including any factory recovery or images are all completely gone..