Related
I have two droid 3's and I rooted them both and went to install a blue theme on one of them from the rom manager app and it worked great, so I did it on my second one, too. When it was in the reboot process it never finished bootoing and it stopped at the red M. All it shows is the boot logo, not the boot animation. I have tried flashing it with rsd lite, but it always fails. Is there any other ideas as to what I should do?
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there. Check this thread on users with the same issue.
Willis111 said:
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there.
Click to expand...
Click to collapse
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
RaTTeDH said:
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
Click to expand...
Click to collapse
I meant rsdlite, have you ever used it with either phone without having an issue? I edited my previous post, added a link you might want to check out.
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
I have never used RSDLite before. So I do not know if it works. But when I am flashing it with the stock 5.6.890 it fails at step 5. It reboots the bootloader. But it fails always at step 5. Let me try the other replys...
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
Click to expand...
Click to collapse
I have downloaded this and tried this. When I run the application moto.fastboot.exe it takes like 30 seconds and when I run the batcch file it immediately finishes and says moto fastboot is not recognized as an internal or external command, operable file or command. And finishes immediately. Sigh.
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
Click to expand...
Click to collapse
The unbrick script will flash a vzw rom to your xt860 and have you stuck at the M logo anyways so I wouldn't suggest trying that. If you haven't used rsdlite before and are having trouble with it now you probably need to install the drivers from the motohelper software.
1./ download the drivers (from motorola)
2./ shutdown phone and turn it on by hold m + power
3./ select ap fastboot mode, enter and plug your phone into the computer ignoring any add new hardware
4./ start the driver install and follow it through
5./ unplug and replug your phone with computer leaving it fastboot mode.
Rsdlite should show your device under listed devices when you start it up at this point and allow you to flash w/e rom. I would suggest using the iucell or brazil retail fastboot files from the xt860 fastboot thread to get your phone up.
I fixed it using CMD in Windows flashing some stuff. Thanks guys!
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
New member here. I just got the phone today, and it's activated, running 5.0. When I check for an update, it shows that there is one, and I download the update. However, after the phone restarts to begin the update, it stops on the system installation screen (it says "error" very quickly, and the android falls over). When the phone restarts, it says that the update couldn't be installed. I've wiped the cache and have done a factory reset, but neither work. Any help would be much appreciated.
Update: Tier 2 tech support from Verizon says the phone has been rooted (I bought the phone used). Is there any way to completely unroot the phone?
Usually a root program can unroot the phone, like if that phone have the root program "SuperSu" on it, there is an unroot function within the program. However, this is not recommended, when the rooting is done and you don't know what the original owners did, there are probably other system files that were changed and the OTA update will detect it and it won't work regardless.
What you should do is flash the factory stock firmware for the device. This will completely return the phone to stock 5.0 and also erase everything in the phone:
1. Download the adb/fastboot files, which is the program used to flash firmwares to android devices:
http://rootjunkysdl.com/?device=Adb Fastboot Files
2. Download the Verizon 5.0 stock firmware:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
3. Download and install the Motorola fastboot driver:
http://forum.xda-developers.com/showpost.php?p=59139823&postcount=2
4. Boot the phone into fastboot mode:
While the phone is turned off, press and hold Vol - and Power. Release Power while still holding Vol - and you will see the bootloader menu appears. Connect the phone to the computer and leave it on this menu, here you can use fastboot commands.
Your computer will begin to install the fastboot driver for your phone right now, go to Computer's Device Manager and make sure you see in top of the list "Android device" and then "Motorola ADB Interface" below it, or something very similar related to ADB.
5. Extract both the files from the ADB/Fastboot files (step 1) and files from the Verizon firmware (step 2) into the same folder. Run the batch file "XT1096_5.0_LXE22.46.11_cid2_CFC.xml.bat", it will run a series of commands that will wipe the phone and install the stock firmware. If all the commands ran successfully you have a fresh install like out of the box.
Note: In the bat file, there is a command called "fastboot erase userdata", this command delete all of the user's apps and files, if you want to keep them you can delete that line from the bat file, however, you might get an error later on if your apps data does match with the version of the firmware you just flashed on the phone (in which case you can have to boot into recovery and wipe data (which will wipe everything) or wipe cache to fix the errors.
6. After installation is done, press Vol+ to select "Normal Power up". For some goofy reason, Vol+ is the select key Motorola phones, not Power. Now you can try doing the OTA update again.
Warning: Do not install the older version firmware (4.4.4) to your phone. There are reports from people who downgrade the version on their Motorola and when they receive over the air update it hard brick their device.
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Has Pie come to the US officially yet? I feel like I have been waiting forever for it.
I am currently on OPSS27.104-92-4 and the January security patch.
I purchased my phone unlocked from BestBuy and using it on Xfinity Mobile, does any of this effect my update schedule?
Has anyone got the Pie update or any other security updates for their RET US g6?
You can find it here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/
pdloud said:
You can find it here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/
Click to expand...
Click to collapse
Attempted this and it failed. Through ADB, it says "Signature Verification Failed" and through the "Motorola Update Services check storage permissions" way, it doesn't recognize the file. Any pointers?
mkollersms said:
Attempted this and it failed. Through ADB, it says "Signature Verification Failed" and through the "Motorola Update Services check storage permissions" way, it doesn't recognize the file. Any pointers?
Click to expand...
Click to collapse
You have to flash it with either Fastboot or RSDLite.
Ragarianok said:
You have to flash it with either Fastboot or RSDLite.
Click to expand...
Click to collapse
That explains it. Thanks for the info. Not ready to unlock the bootloader on my handset yet, but if Motorola/Lenovo doesn't come up with the update by June 15th...
mkollersms said:
That explains it. Thanks for the info. Not ready to unlock the bootloader on my handset yet, but if Motorola/Lenovo doesn't come up with the update by June 15th...
Click to expand...
Click to collapse
You shouldn't need to unlock anything.
Ragarianok said:
You shouldn't need to unlock anything.
Click to expand...
Click to collapse
What's the fastboot command to apply the update? I'm looking through the guides but I can't find it offhand, and the guides for other devices insist it has to be. If you can help expedite this, I would be super grateful.
mkollersms said:
What's the fastboot command to apply the update? I'm looking through the guides but I can't find it offhand, and the guides for other devices insist it has to be. If you can help expedite this, I would be super grateful.
Click to expand...
Click to collapse
Unzip it and look at the flashfile.xml and servicefile.xml for the commands. You can use RSDlite to flash it or the XML to batch program to make a .bat file to flash it.
Downloaded the file from the link in post #2 this morning and used RSD Lite and the service file. Quick, easy and painless. Didn't even erase data. Not my daily driver but nice to not have to go through the setup process after the flash.
Bootloader still locked.
SuperNoob help please
jfalls63 said:
Downloaded the file from the link in post #2 this morning and used RSD Lite and the service file. Quick, easy and painless. Didn't even erase data. Not my daily driver but nice to not have to go through the setup process after the flash.
Bootloader still locked.
Click to expand...
Click to collapse
PLEASE don't thrash me... can someone please explain the above steps in plain English so that I can get this update installed? I'm not an idiot, just need a quick set of instructions to make the above work.
(And you'll thank me for focussing on being a physician and not a phone nerd when you come see me at my office :angel: )
You can get RSD Lite and Motorola USB drivers for Windows PC here.
https://forum.xda-developers.com/ge...e-firmware-t3042687/post59348530#post59348530
RSD Lite is a flash tool Motorola devices.
Basically, I downloaded the last firmware file listed in the link and unzipped the file. Opened RSD Lite on my PC and connected the phone setting USB connection to File Transfer mode. In RSD Lite, at the top is a block for File name. Click on the horizontal 3 dot menu next to it and navigate to the the unzipped firmware file. I selected the service file then select start. Phone rebooted into fastboot mode and RSD Lite flashed the firmware.
Phone rebooted when complete. I had already enabled USB debugging in Developer Options.
jfalls63 said:
You can get RSD Lite and Motorola USB drivers for Windows PC here.
https://forum.xda-developers.com/ge...e-firmware-t3042687/post59348530#post59348530
RSD Lite is a flash tool Motorola devices.
Basically, I downloaded the last firmware file listed in the link and unzipped the file. Opened RSD Lite on my PC and connected the phone setting USB connection to File Transfer mode. In RSD Lite, at the top is a block for File name. Click on the horizontal 3 dot menu next to it and navigate to the the unzipped firmware file. I selected the service file then select start. Phone rebooted into fastboot mode and RSD Lite flashed the firmware.
Phone rebooted when complete. I had already enabled USB debugging in Developer Options.
Click to expand...
Click to collapse
<:cyclops:*JOY*:cyclops:> Thank you!! I'll snag a PC and try it.
jfalls63 said:
Downloaded the file from the link in post #2 this morning and used RSD Lite and the service file. Quick, easy and painless. Didn't even erase data. Not my daily driver but nice to not have to go through the setup process after the flash.
Bootloader still locked.
Click to expand...
Click to collapse
Just one question, does it pass safenet?
Yes. Your bootloader does not have to be unlocked. Everything is still official.
mastertech2 said:
<:cyclops:*JOY*:cyclops:> Thank you!! I'll snag a PC and try it.
Click to expand...
Click to collapse
This took about 15-20 minutes and worked perfectly. Thank You!
jfalls63 said:
You can get RSD Lite and Motorola USB drivers for Windows PC here.
https://forum.xda-developers.com/ge...e-firmware-t3042687/post59348530#post59348530
RSD Lite is a flash tool Motorola devices.
Basically, I downloaded the last firmware file listed in the link and unzipped the file. Opened RSD Lite on my PC and connected the phone setting USB connection to File Transfer mode. In RSD Lite, at the top is a block for File name. Click on the horizontal 3 dot menu next to it and navigate to the the unzipped firmware file. I selected the service file then select start. Phone rebooted into fastboot mode and RSD Lite flashed the firmware.
Phone rebooted when complete. I had already enabled USB debugging in Developer Options.
Click to expand...
Click to collapse
I rooted my phone last year and have not updated the firmware. Does it matter what version of firmware I am on to install the latest, the last, zip file listed from here using RSD Lite:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/
If I do nothing after installing the last firmware listed above with RSD LIte, can the phone then accept OTA updates in the future if I do not root again? Or do I have to use RSD LIte again to install updates?
Are these instructions good? Their link to firmware is broken so unsure.
https://www.androidinfotech.com/motorola-g6-pie/
I appreciate the guidance. Have read many pages on several threads and it seems RSD Lite is the way to go. Just uncertain of a few details....
It's a complete firmware flash, not a partial update so it shouldn't matter what firmware version you are currently on. May want to get a second opinion though.
Should put you back to stock with your bootloader still unlocked. OTA's shouldn't be a problem if Motorola ever decides to release anymore.
RSD Lite does not see phone. Reinstalled Moto device drivers. Mini ADB Fastboot sees phone and can issue commands. Phone in Bootloader shows "USB connected". Rebooted phone, computers, reset usb cable, tried different computer USB port....
Tried the above instructions:
"RSD Lite is a flash tool Motorola devices.
Basically, I downloaded the last firmware file listed in the link and unzipped the file. Opened RSD Lite on my PC and connected the phone setting USB connection to File Transfer mode. In RSD Lite, at the top is a block for File name. Click on the horizontal 3 dot menu next to it and navigate to the the unzipped firmware file. I selected the service file then select start. Phone rebooted into fastboot mode and RSD Lite flashed the firmware.
Phone rebooted when complete. I had already enabled USB debugging in Developer Options. "
And these instructions that say to put phone in Fastboot Mode ( RSD Lite Method). The phone does diplay "USB Connected " in Fastboot Mode:
https://www.androidinfotech.com/motorola-g6-pie/
Android-Jack said:
RSD Lite does not see phone. Reinstalled Moto device drivers. Mini ADB Fastboot sees phone and can issue commands. Phone in Bootloader shows "USB connected". Rebooted phone, computers, reset usb cable, tried different computer USB port....
Tried the above instructions:
"RSD Lite is a flash tool Motorola devices.
Basically, I downloaded the last firmware file listed in the link and unzipped the file. Opened RSD Lite on my PC and connected the phone setting USB connection to File Transfer mode. In RSD Lite, at the top is a block for File name. Click on the horizontal 3 dot menu next to it and navigate to the the unzipped firmware file. I selected the service file then select start. Phone rebooted into fastboot mode and RSD Lite flashed the firmware.
Phone rebooted when complete. I had already enabled USB debugging in Developer Options. "
And these instructions that say to put phone in Fastboot Mode ( RSD Lite Method). The phone does display "USB Connected " in Fastboot Mode:
Click to expand...
Click to collapse
RSD Lite can detect my G6 while the phone is just on the lock screen, connected via USB and not even in file transfer mode using RSD Lite 6.2.4 and Windows 7 x64. RSD Lite will automatically detect the phone and list it in the program. The phone should NOT be in USB debugging mode - RSD Lite cannot detect my phone in USB debugging mode. Also, you have to be using a USB cable that is capable of file transfer. Not all USB-C cables are capable of file transfer. I DO have "Enable OEM unlocking" enabled in developer options but I have not unlocked my bootloader and it's not necessary to do that if you're flashing a signed ROM from Motorola.
In RSD Lite, you pick the "flashfile" or "servicefile" xml file in the file picker from the unzipped ROM and click start. Note that "Flashfile.xml" by default will erase the userdata and cache partitions - basically resetting your device. You can modify the flashfile.xml file to remove the erase steps if you want, but I wouldn't try to flash oreo -> pie without erasing those partitions personally.
The official Pie RETUS release is the file dated 7-16-19 on the lolinet mirror. I was able to update from a prerelease Pie ROM (the 5-19 one on lolinet) without erasing my userdata and cache partitions and it upgraded fine.
ETA: Those instructions at AndroidInfoTech are convoluted or just wrong. RSD Lite works fine without being in fastboot or having USB debugging enabled. It handles rebooting the phone and going into fastboot automatically.
mjwise said:
RSD Lite can detect my G6 while the phone is just on the lock screen, connected via USB and not even in file transfer mode using RSD Lite 6.2.4 and Windows 7 x64. RSD Lite will automatically detect the phone and list it in the program. The phone should NOT be in USB debugging mode - RSD Lite cannot detect my phone in USB debugging mode. Also, you have to be using a USB cable that is capable of file transfer. Not all USB-C cables are capable of file transfer. I DO have "Enable OEM unlocking" enabled in developer options but I have not unlocked my bootloader and it's not necessary to do that if you're flashing a signed ROM from Motorola.
In RSD Lite, you pick the "flashfile" or "servicefile" xml file in the file picker from the unzipped ROM and click start. Note that "Flashfile.xml" by default will erase the userdata and cache partitions - basically resetting your device. You can modify the flashfile.xml file to remove the erase steps if you want, but I wouldn't try to flash oreo -> pie without erasing those partitions personally.
The official Pie RETUS release is the file dated 7-16-19 on the lolinet mirror. I was able to update from a prerelease Pie ROM (the 5-19 one on lolinet) without erasing my userdata and cache partitions and it upgraded fine.
ETA: Those instructions at AndroidInfoTech are convoluted or just wrong. RSD Lite works fine without being in fastboot or having USB debugging enabled. It handles rebooting the phone and going into fastboot automatically.
Click to expand...
Click to collapse
Turned off USB Debugging, not in file transfer mode rebooted phone and left it in locked screen. RSD still does not see it. The cable is the original and has transferred many files and was used to root the phone. And Fastboot sees phone and allows me to make commands.
RSD Lite 6.2.4
Moto Drivers for 64 bit Win 10. BUT, when in Device Manager/Android Devices/Motorola ADB Interface it says "Driver Date: 7/7/2013" Dont know if this is good or correct date since ADB Fastboot works. I reinstalled Moto device drivers twice and same date appears.
The computer definitely sees the phone. Everytime the usb cable is connected/disconnected it asks what to do next...