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...
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!
What's up guys. I recently bought a 2014 moto x us cellular. Turns out it was stuck asking for the last Google sign in. I decided to flash back to stock using fastboot. Used motofastboot and entered all the commands correctly, but now it says failed to boot or boot up failed after flashing the m Motorola screen for a split second. It also says failed to validate system image in pink. I tried both the 5.0 and 5.1 factory firmware. Fastboot didn't say any errors. I can't get rsd to see it. Any suggestions? Do I need to flash all 9 of the system.img_sparsechunk files?
If RSD Lite cannot see your phone it might have to do with no drivers installed or improperly installed.
You'll have to deinstall any drivers related to Motorola and/or ADB cleanly using USBDeview http://www.majorgeeks.com/files/details/usbdeview.html and DriverStore Explorer [RAPR.exe] https://driverstoreexplorer.codeplex.com/releases/view/99694 .
1.) In USBDeview you'll want to highlight anything related to Motorola, ADB, Google ADB driver, Samsung ADB driver etc and then right click and select 'Uninstall Selected Devices'. Done with this program.
2.) In DriverStore Explorer [RAPR.exe] click on Enumerate, then you'll also want to select the checkboxes next to anything related to items listed in step 1, then on the right side choose 'Force Deletion' box, then click Delete Package. Done with this program.
3.) Restart Windows
4.) Download Lollipop 5.0.2 for USC from http://motofirmware.center/files/file/169-victara_usc_502_lxe2246-33_cid9_cfcxmlzip/ or Lollipop 5.1 for USC from http://motofirmware.center/files/file/248-victara_usc_51_lpe2332-213_cid9_cfcxmlzip/ depending on your current firmware version.
5.) Install Motorola USB drivers for our device (#82) from http://androidxda.com/download-motorola-usb-drivers
6.) Connect your phone, let Windows install the necessary drivers.
7.) Run RSD Lite, browse for the firmware you downloaded earlier, choose 'Decompress and Flash' on the box that pops up. *Do not try to downgrade Lollipop versions as it will fail and you'll end up with a third of the files flashed before it errors*
8.) Wait for your firmware to flash, no need to wipe after the flash since RSD Lite runs the 'erase userdata' & 'erase cache' commands after flashing.
I recommend flashing with RSD Lite since it does everything correctly and automatically. These steps will help make sure your system has Motorola device drivers properly installed.
Try this and let me know if this works. If not, we'll troubleshoot further.
Thanks for such a detailed description man. Drivers are something I always struggle with. I'm downloading everything now and ill try when I get home. I'll let you know how it turns out. Thanx again
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!
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
Hi
I want to flash my Mi 9 Lite by MiFlash v2020.3.14.0 in fastboot mode(Fastboot Update).
My device is unlocked and unroot, I download the latest official tgz ROM and decompress it and run MiFlash and past the ROM address to the MiFlash tool, after refreshing my device is recognized , I click on flash button, but MiFlash tools show me "error:not catch checkpoint (\$fastboot -s.*lock).flash is not done"
Even by going to the configuration menu and removing the text "\$fastboot -s .* lock" from the checkpoint and OK it and then clicking on the flash, the program will quickly show the flash done and show flashing is success, but it is not actually flashed!!!
I have already installed Minimal ADB Fastboot v1.4.3 and device driver, developer options and usb debugging is on.
in CMD I run fastboot devices command and my device is recognized
I even installed TWRP recovery by adb commands
what's the solution?
Why MiFlash does not flash the official ROM and shows error?
How can I flash the official ROM(*.tgz file) in Fastboot?
thanks.
karaj3 said:
Hi
I want to flash my Mi 9 Lite by MiFlash v2020.3.14.0 in fastboot mode(Fastboot Update).
My device is unlocked and unroot, I download the latest official tgz ROM and decompress it and run MiFlash and past the ROM address to the MiFlash tool, after refreshing my device is recognized , I click on flash button, but MiFlash tools show me "error:not catch checkpoint (\$fastboot -s.*lock).flash is not done"
Even by going to the configuration menu and removing the text "\$fastboot -s .* lock" from the checkpoint and OK it and then clicking on the flash, the program will quickly show the flash done and show flashing is success, but it is not actually flashed!!!
I have already installed Minimal ADB Fastboot v1.4.3 and device driver, developer options and usb debugging is on.
in CMD I run fastboot devices command and my device is recognized
I even installed TWRP recovery by adb commands
what's the solution?
Why MiFlash does not flash the official ROM and shows error?
How can I flash the official ROM(*.tgz file) in Fastboot?
thanks.
Click to expand...
Click to collapse
Probably you did something wrong trying to remove that text, you don't need to remove it if your bootloader is unlocked.
You can flash it directly using fastboot commands, or you can flash it through EDL mode too.
SubwayChamp said:
Probably you did something wrong trying to remove that text, you don't need to remove it if your bootloader is unlocked.
You can flash it directly using fastboot commands, or you can flash it through EDL mode too.
Click to expand...
Click to collapse
Thank you for your answer
My device bootloader is unlocked, I also saw and checked it. I did it both when it was text and when I deleted the text, but in fact nothing happened and my device did not flash and only remained in the same fastboot mode until I restarted it and it started normally.
I even tried the new version of Mi Flash Tool v20210226 and got the same result as before.
I downloaded 3 different versions for mi 9 lite from the official site, https://c.mi.com/oc/miuidownload/detail?guide=2, and as I explained, it was.
even I downloaded other regional Roms but the same result...
you said : You can flash it directly using fastboot commands, or you can flash it through EDL mode too.
How can I flash an official ROM with the *.tgz extension(in fastboot mode or other mode)?
karaj3 said:
Thank you for your answer
My device bootloader is unlocked, I also saw and checked it. I did it both when it was text and when I deleted the text, but in fact nothing happened and my device did not flash and only remained in the same fastboot mode until I restarted it and it started normally.
I even tried the new version of Mi Flash Tool v20210226 and got the same result as before.
I downloaded 3 different versions for mi 9 lite from the official site, https://c.mi.com/oc/miuidownload/detail?guide=2, and as I explained, it was.
even I downloaded other regional Roms but the same result...
you said : You can flash it directly using fastboot commands, or you can flash it through EDL mode too.
How can I flash an official ROM with the *.tgz extension(in fastboot mode or other mode)?
Click to expand...
Click to collapse
Mm, Maybe you are trying to use the fastboot ROM through Mi Flash tool without firstly decompressing it?
You need to decompress first the tar.gz file, you will find inside all the image partitions, the scripts needed.
As you can see in the images in this thread, the files have to be accessible for the tool to can load them https://androidmtk.com/use-xiaomi-mi-flash-tool
This is the simplest way, using Mi Flash tool, you can use it in fastboot (if unlocked) or in EDL mode (no matter locked or not). Take care to not choose the option "relock" device if you don't want to do that.
For the fastboot commands you require to decompress the files and execute simply fastboot flashall -w this will format data and update your device. Sometimes this simple command doesn't work, then you can edit the flashall.bat file, line-by-line, to the scripts being executed.
SubwayChamp said:
Mm, Maybe you are trying to use the fastboot ROM through Mi Flash tool without firstly decompressing it?
You need to decompress first the tar.gz file, you will find inside all the image partitions, the scripts needed.
As you can see in the images in this thread, the files have to be accessible for the tool to can load them https://androidmtk.com/use-xiaomi-mi-flash-tool
This is the simplest way, using Mi Flash tool, you can use it in fastboot (if unlocked) or in EDL mode (no matter locked or not). Take care to not choose the option "relock" device if you don't want to do that.
For the fastboot commands you require to decompress the files and execute simply fastboot flashall -w this will format data and update your device. Sometimes this simple command doesn't work, then you can edit the flashall.bat file, line-by-line, to the scripts being executed.
Click to expand...
Click to collapse
No.
I decompress first the tar.gz file! I wrote all my actions in post 1 and post 3.
I followed the instructions written on the official Xiaomi page(https://c.mi.com/oc/miuidownload/detail?guide=2)
how can I flash the official ROM in fastboot mode or any other mode?
Please write a guide for me. my device is Mi 9 Lite.
thank you.
karaj3 said:
No.
I decompress first the tar.gz file! I wrote all my actions in post 1 and post 3.
I followed the instructions written on the official Xiaomi page(https://c.mi.com/oc/miuidownload/detail?guide=2)
how can I flash the official ROM in fastboot mode or any other mode?
Please write a guide for me. my device is Mi 9 Lite.
thank you.
Click to expand...
Click to collapse
You can flash through EDL mode the same way as it is in the guide you followed, the main difference is that you have to put your device in EDL mode to perform the operation.
As your device is unlocked you can put it in EDL mode without the need to disassemble the back cover, either using fastboot oem edl or from a device off, pressing both volume buttons at the same time that you connect to the PC, firstly open Windows device manager and check that it is listed as Qualcomm 9008-USB, you need to install this https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
Rom should be unzipped on desktop. Not inside a faulder.... If you unzipped it inside faulder error will come up
Noexcusses said:
Rom should be unzipped on desktop. Not inside a faulder.... If you unzipped it inside faulder error will come up
Click to expand...
Click to collapse
Thank you for your answer, but it still showed the same error
karaj3 said:
Thank you for your answer, but it still showed the same error
Click to expand...
Click to collapse
The folder can be placed in any side, even I always have my tool installed in the main drive (C) and the Miui ROM in another partition (D) you have to suppress all the spaces in the names and lastly browse where the images' directory is, not inside but where it is the images directory and the scripts.
What about EDL, did you achieve to get it? Upload some screenshot, from the browser files and from the error you are getting, I'm sure it's easy to fix it, maybe you are missing something.
SubwayChamp said:
The folder can be placed in any side, even I always have my tool installed in the main drive (C) and the Miui ROM in another partition (D) you have to suppress all the spaces in the names and lastly browse where the images' directory is, not inside but where it is the images directory and the scripts.
What about EDL, did you achieve to get it? Upload some screenshot, from the browser files and from the error you are getting, I'm sure it's easy to fix it, maybe you are missing something.
Click to expand...
Click to collapse
I tried everything and the same error was shown!
I did not try the EDL method because I am not a professional user and I want to use safe, common and easy methods.
karaj3 said:
I tried everything and the same error was shown!
I did not try the EDL method because I am not a professional user and I want to use safe, common and easy methods.
Click to expand...
Click to collapse
Don't use "Clean all & Lock" at least till you solve it.
EDL method is simple to use if you have your bootloader unlocked (this is one of the reasons why you don't have to lock it right now).
To use the EDL method you just have to power off completely, then while you connect the device to the PC press both volume buttons.
Before install the Qualcomm 9008 USB drivers.