Related
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
I have a T-Mobile XT1053, and got the 5.1 update which failed several times. I assumed it was because of something I had done to my phone in the past even though I am on the stock recovery, so I opted to go back to stock everything. Here's where my problems started. Every set of instructions sent me to download the 4.3 image, and now after reading posts in this forum I find that I should never downgrade (I was on 4.4.4). I ended up getting an update to work (gpt.bin failed), and after booting fine, I was told there was an update (4.4) which I took. After the update and reboot, my phone does not appear to turn on. The only thing that tells me I may not be 100% screwed is that when plugged into my Windows machine, if I hold the power button, I hear the disconnect sound, then the reconnect sound. I have tried to run fastboot and adb to look for devices, but neither finds anything. So....is my phone bricked?
mr2400 said:
I have a T-Mobile XT1053, and got the 5.1 update which failed several times. I assumed it was because of something I had done to my phone in the past even though I am on the stock recovery, so I opted to go back to stock everything. Here's where my problems started. Every set of instructions sent me to download the 4.3 image, and now after reading posts in this forum I find that I should never downgrade (I was on 4.4.4). I ended up getting an update to work (gpt.bin failed), and after booting fine, I was told there was an update (4.4) which I took. After the update and reboot, my phone does not appear to turn on. The only thing that tells me I may not be 100% screwed is that when plugged into my Windows machine, if I hold the power button, I hear the disconnect sound, then the reconnect sound. I have tried to run fastboot and adb to look for devices, but neither finds anything. So....is my phone bricked?
Click to expand...
Click to collapse
1. Phone enter fastboot?
2. If yes, enter recovery?
3. If no, when you connect the phone to pc appear something in devices?
helloimseba311 said:
1. Phone enter fastboot?
2. If yes, enter recovery?
3. If no, when you connect the phone to pc appear something in devices?
Click to expand...
Click to collapse
The phone does not enter fastboot but when I plug it into my computer it connects and makes the connect sound.
This thread seemed like it might be the ticket. I ran everything as described, and it seemed successful, but no fastboot.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I also followed this thread with no luck. I get all kinds of python errors and have not had a chance to write it up for the poster to look at.
http://forum.xda-developers.com/showpost.php?p=60401909&postcount=14
mr2400 said:
The phone does not enter fastboot but when I plug it into my computer it connects and makes the connect sound.
This thread seemed like it might be the ticket. I ran everything as described, and it seemed successful, but no fastboot.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I also followed this thread with no luck. I get all kinds of python errors and have not had a chance to write it up for the poster to look at.
http://forum.xda-developers.com/showpost.php?p=60401909&postcount=14
Click to expand...
Click to collapse
Ok, we are going to revive your phone
If your phone connects to the pc and make a sound, you are saved
Im going to search some files in my pc, wait for me, you can read a bit
Enviado desde mi Moto X mediante Tapatalk
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
mr2400 said:
The phone does not enter fastboot but when I plug it into my computer it connects and makes the connect sound.
This thread seemed like it might be the ticket. I ran everything as described, and it seemed successful, but no fastboot.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I also followed this thread with no luck. I get all kinds of python errors and have not had a chance to write it up for the poster to look at.
http://forum.xda-developers.com/showpost.php?p=60401909&postcount=14
Click to expand...
Click to collapse
Have you tried the blankflash method?
Enviado desde mi Moto X mediante Tapatalk
helloimseba311 said:
Ok, we are going to revive your phone
If your phone connects to the pc and make a sound, you are saved
Im going to search some files in my pc, wait for me, you can read a bit
Enviado desde mi Moto X mediante Tapatalk
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
Have you tried the blankflash method?
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
I believe I have, is that the method describe in the first link I posted? If so, everything seemed to go perfect, but I still have no fastboot.
Your phone appear like qualcomm?
Have you flashed blankflash?
If yes, have you flashed motoboot and gpt?
mr2400 said:
I believe I have, is that the method describe in the first link I posted? If so, everything seemed to go perfect, but I still have no fastboot.
Click to expand...
Click to collapse
Enviado desde mi Moto X mediante Tapatalk
helloimseba311 said:
Your phone appear like qualcomm?
Have you flashed blankflash?
If yes, have you flashed motoboot and gpt?
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
My phone does show up as Qualcomm HS-USB QDLoader 9008 (COM3).
I believe I only flashed blankflash using this command, and there were no errors. "qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o"
mr2400 said:
My phone does show up as Qualcomm HS-USB QDLoader 9008 (COM3).
I believe I only flashed blankflash using this command, and there were no errors. "qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o"
Click to expand...
Click to collapse
Ok you flashed it, do this
Ok, do you have the fastboot binary installed?
If so, please do this:
From the bootloader screen: type the following commands:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
NOW try RSD Lite again.
Here's the explaination: What we are doing is JUST flashing the bootloader and the partition table (gpt.bin). Then we are immediately rebooting the system back to the bootloader so the device can LOAD the bootloader and the new partition table, BEFORE we proceed with flashing the rest of the partitions.
I've helped several (but not all!!!) people recovery by doing this. It may not work for you, but it is worth a try. Good Luck.
Click to expand...
Click to collapse
helloimseba311 said:
Ok you flashed it, do this
Click to expand...
Click to collapse
Well, that's my problem. After doing the blankflash, I still don't have fastboot. My phone still connects as Qualcomm HS-USB QDLoader 9008 (COM3) but I see nothing on the screen, and when I run fastboot devices I get nothing.
mr2400 said:
Well, that's my problem. After doing the blankflash, I still don't have fastboot. My phone still connects as Qualcomm HS-USB QDLoader 9008 (COM3) but I see nothing on the screen, and when I run fastboot devices I get nothing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/orig-development/bootloader-tool-motoflasher-t2959081
See this thread and try, last solution
helloimseba311 said:
http://forum.xda-developers.com/moto-x/orig-development/bootloader-tool-motoflasher-t2959081
See this thread and try, last solution
Click to expand...
Click to collapse
Awesome, I will try this a little later today!
helloimseba311 said:
http://forum.xda-developers.com/moto-x/orig-development/bootloader-tool-motoflasher-t2959081
See this thread and try, last solution
Click to expand...
Click to collapse
I have everything setup as the docuements say, but am getting the following. I think it may be a configuration issue with MotoFlasher because I see the files it's looking for in C:\Program Files (x86)\MotoFlasher\Component\ghost_***. I will post up in that forum and perhaps the creator will know what the problem is.
Code:
**** BASIC INFORMATION ****
SYSTEM: Aplication Started at: 23/06/15 08:57
SYSTEM: OS: Microsoft Windows NT 6.2.9200.0
ARCHITECTURE: x64
ASSEMBLY: MotoFlasher Version: 2.1.2.2
SYSTEM: Device Selected: Moto X v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: Emergency download enumeration detected on port - com4
OUTPUT: The following files are missing!
OUTPUT: MPRG8960.hex
OUTPUT: qflash.exe
OUTPUT: MSM8960_bootloader_singleimage.bin
OUTPUT:
OUTPUT:
Here's my other post: http://forum.xda-developers.com/showpost.php?p=61514368&postcount=36
mr2400 said:
I have everything setup as the docuements say, but am getting the following. I think it may be a configuration issue with MotoFlasher because I see the files it's looking for in C:\Program Files (x86)\MotoFlasher\Component\ghost_***. I will post up in that forum and perhaps the creator will know what the problem is.
Code:
**** BASIC INFORMATION ****
SYSTEM: Aplication Started at: 23/06/15 08:57
SYSTEM: OS: Microsoft Windows NT 6.2.9200.0
ARCHITECTURE: x64
ASSEMBLY: MotoFlasher Version: 2.1.2.2
SYSTEM: Device Selected: Moto X v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: Emergency download enumeration detected on port - com4
OUTPUT: The following files are missing!
OUTPUT: MPRG8960.hex
OUTPUT: qflash.exe
OUTPUT: MSM8960_bootloader_singleimage.bin
OUTPUT:
OUTPUT:
Click to expand...
Click to collapse
Was 4.4.2 your last firmware? Wasnt lollipop?
Try it again and see where it fails, or you can se the FAQ in the main thread
Enviado desde mi Moto X mediante Tapatalk
helloimseba311 said:
Was 4.4.2 your last firmware? Wasnt lollipop?
Try it again and see where it fails, or you can se the FAQ in the main thread
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
I believe my progression was Failed Lollipop OTA --> Downgrade from 4.4.4 to 4.4.2 (yeah I know...I'm a dumbass) --> Failed 4.4.4 OTA --> Won't turn on. I tried MotoFlasher several times with all of the different versions of Android with the same error. The FAQ says nothing of this kind of error and says I will see different messages if I have the wrong version of Android picked. My assumption is that I have a configuration issue with MotoFlasher and it's not seeing the files that it needs to flash in C:\Program Files (x86)\MotoFlasher\Component\ghost_***. I do appreciate all of the help though, and I still don't think I have exhausted all of my options. Let's hope someone has seen this issue before .
mr2400 said:
I believe my progression was Failed Lollipop OTA --> Downgrade from 4.4.4 to 4.4.2 (yeah I know...I'm a dumbass) --> Failed 4.4.4 OTA --> Won't turn on. I tried MotoFlasher several times with all of the different versions of Android with the same error. The FAQ says nothing of this kind of error and says I will see different messages if I have the wrong version of Android picked. My assumption is that I have a configuration issue with MotoFlasher and it's not seeing the files that it needs to flash in C:\Program Files (x86)\MotoFlasher\Component\ghost_***. I do appreciate all of the help though, and I still don't think I have exhausted all of my options. Let's hope someone has seen this issue before .
Click to expand...
Click to collapse
You must be more carefully haha
Have you tried to put the files into the motoflasher folder?
Enviado desde mi Moto X mediante Tapatalk
hi folks,
I'm newbie to rooting phone. Recently installed CM 12.1 on my Moto XT 1052. now i wanna change to some other os. so i did the data and apps backup by using TWRP. But suddenly my phone is getting automatically restarting continuously and not able to use it..
what i need to do for getting back my phone to normal? Kindly Help me guys !! \
Thanks in Advance !!
Does it automatically restart even while in TWTP? If not then try a factory reset or advanced wipe of data, cache and dalvik cache only.
If that doesn't fix it then download other ROM in a PC and then copy it to your phone using the USB cable and flash.
Enviado desde mi XT1053 mediante Tapatalk
lavero.burgos said:
Does it automatically restart even while in TWTP? If not then try a factory reset or advanced wipe of data, cache and dalvik cache only.
If that doesn't fix it then download other ROM in a PC and then copy it to your phone using the USB cable and flash.
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
Thanks a lot for your reply !! sorry for late response even if i go to TWRP still facing the issue and while restarting USB connectivity is not working.. what do i do?!?
rokersragu said:
Thanks a lot for your reply !! sorry for late response even if i go to TWRP still facing the issue and while restarting USB connectivity is not working.. what do i do?!?
Click to expand...
Click to collapse
First boot into recovery and WIPE INTERNAL (MEDIA) STORAGE, reboot to recovery again do a factory reset, if that doesn't fix it then i would recommend you to download a full stock ROM according to the phone model you own.
Once downloaded and uncompressed copy the files to the adb tools folder (Usually ADB is placed or installed under C:/ on Windows) put your phone into fastboot mode (Vol Down + Power button), leave it like that for at least 5 minutes to make sure it doesn't reboot automatically.
If it doesn't reboot then proceed to flash the stock ROM (you'll need drivers and fastboot/mfastboot) but if it does reboot or you can't get into fastboot mode then check this thread: http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Enviado desde mi XT1053 mediante Tapatalk
lavero.burgos said:
First boot into recovery and WIPE INTERNAL (MEDIA) STORAGE, reboot to recovery again do a factory reset, if that doesn't fix it then i would recommend you to download a full stock ROM according to the phone model you own.
Once downloaded and uncompressed copy the files to the adb tools folder (Usually ADB is placed or installed under C:/ on Windows) put your phone into fastboot mode (Vol Down + Power button), leave it like that for at least 5 minutes to make sure it doesn't reboot automatically.
If it doesn't reboot then proceed to flash the stock ROM (you'll need drivers and fastboot/mfastboot) but if it does reboot or you can't get into fastboot mode then check this thread: http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
Thank you so much man !! U helped me lot.. I did what u said. Now its working fine.. Once again thanks man !!:good:
Here we go:
1- Today i got a new phone
2- Wanted to remove the Google search bar and disable google app
3- Restart and the phone screen is very different like another version, so i decide to do a soft reboot
4- Phone stuck on auto loop
5- Try recovery mode, dont work
6- Fastboot works
7- I download new room jasmine_global_images_V10.0.12.0.PDIMIXM_20190712.0000.00_9.0_1e580ee45b
8- Download Miflash and Minimal ADB and fastboot.
9- Plug the phone in pc
10- Unlocks OEM with app
11- Opened Mi flash
12- Miflash have installed all the drivers
13- When i click on refresh the Fastboot icon(the android and the soviet cat) dissapears and the only thing i have is in one corner "press any key to shutdown"
Important data:
-i have windows 10 with usb 3.1 and 2.0
-USB debugg is locked
-By pure luck once i managed to do a full boot sequence but when it finished the layout of the screen was different, like another version and i started updating it, after a couple of updates it stuck again on bootloop.
- i have no idea what was the original version on the room but in the last point and in nº 3 it was 10.0.7.
- i have nothing that i cannot recover so i dont mind wiping out my userdata
-i have considered a test point but i dont know if it going to work
-return it to amazon its my last ressort
- i read about the issues in december and january with the bootloop but i tried everything
-i have acces to a computer with linux
-its very difficult to start the fastboot logo/menu and almost impossible the recovery mode, it almost always ends with phone booting, when i plug it onto my pc it start with the bootloop.
-sometimes when i click on refresh while the phone with the screen in black or starting up with the android one logo it changes to fastloop automatically
- also tried a hard resset and nothing changed
I have no clue what to do, should i do the test point, ask for another in amazon, spray it with holy water??
Sorry for the possible typos and all the numbers i wanted to explain myself and to put some order in my head.
Please help and Thanks in advance
Fastboot rom
Try FASTBOOT method to unbrick your mi a2,
Karthickvel1988 said:
Try FASTBOOT method to unbrick your mi a2,
Click to expand...
Click to collapse
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
SrBisectriz said:
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
Click to expand...
Click to collapse
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
K9998 said:
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
SrBisectriz said:
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
Click to expand...
Click to collapse
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
K9998 said:
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
I tried these and only worked once or twice
But mi Flash did not recognise the phone
SrBisectriz said:
I tried these and only worked once or twice
But mi Flash did not recognise the phone
Click to expand...
Click to collapse
Mi flash required both unlock to do the work.
Sent from my Mi A2 using Tapatalk
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
priviet.toledo said:
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
I had a similar problem just now - could not do anything in fastboot mode, LMSA failed as well. To solve it, I switched to another PC, and stopped using USB3 to USB-C custom cable, and used the original one I got with the phone (USB-C to USB-C). So my guess is, you need to connect to the PC with the original cable, directly, or just with a better cable than the one you were trying with.
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Gingerale2020 said:
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all [/Code
[url]https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039[/url]