It is assumed that you are on Kitkat with unlocked bootloader and rooted. Here is what I did (this is on Linux, but for Windows the instructions remain the same):
0. Backup first.
a. Use TWRP to do a full back up of your current ROM. Use 2.8.2.0 from Luca here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
b. Use titanium backup to back up all your apps and their data.
Just as a precaution. This guide will keep your data and apps intact...
1. Get the Lollipop OTA
a. After the OTA download was complete, I kept on postponing the install. The downloaded ZIP was in /cache folder, which I could read when rooted. So, the first step was to adb pull it onto my PC to save it for eternity.
OR
b. If you don't have the OTA in your cache folder, download it from forums here. Left as an exercise for the reader....
2. Go back to stock Kitkat as much as you can without destroying the data partition and losing apps and settings.
a. Get your current stock ROM and unzip it in a folder
b. adb reboot bootloader, and change directory to the folder where you unzipped the stock files.
c. restore to stock without losing the /data
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
3. Sideload the OTA ZIP.
a. adb reboot recovery - this will put you into stock recovery. Press Vol UP while Power is pressed. It will be give you a menu. Vol Down to "Install from ADB" and Power (or Vol Up, don't remember, I think this changed with Lollipop) to select.
b. Once the phone is in sideload mode ("Install from ADB" mode), do 'adb sideload <ZIP NAME>'
c. Wait....wait some more. It will take quite a bit.
4. Boot back. It should start upgrading your apps you had before the upgrade with "Android upgrading..." dialog.
5. Go on and try other OTA updates (which don't work right now). Or load your favorite root method and/or TWRP, and create another backup point for your Lollipop install with all your apps and settings.
For me, I am at 22.11.6 (5.0.0 with 2 OTAs missing), rooted and TWRP. Once new OTAs arrive, I will do the same thing again...
Wow, great !
It worked like a charm for me, I even stopped before 3) to reboot and do the ota automatically, succesfully and I didn't lose any data.
Fyi I hat a rooted/xposed xt1032 running 4.4.4 and I installed the 5.0.1 OTA this way (210.12.40 to 220.27.1).
Thanks a lot !
Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you
intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer
when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you
you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond
I have been away from Android for a little while - but I'm coming to sell my Nexus 6, and so I'm attempting to flash the latest OS from google.
I downloaded 6.0.1 from google, and then worked through these steps:
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
Yes, there are more steps, but I just can't get to them! Once I flash system I get the following...
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 25.080s]
writing 'system'...
OKAY [ 7.142s]
sending sparse 'system' (515137 KB)...
OKAY [ 25.155s]
writing 'system'...
OKAY [ 7.346s]
sending sparse 'system' (515644 KB)...
Thats it, thats as far as it ever goes, then I just sit there waiting, waiting, and nothing happens.
Any suggestions?
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
dahawthorne said:
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
Click to expand...
Click to collapse
Good call on the movement of files to the adb/fastboot folder, as that is what I do when flashing these files, and the flash-all.bat potentially causing his issues.
RMarkwald said:
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Click to expand...
Click to collapse
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Mongo23ny said:
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Click to expand...
Click to collapse
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
RMarkwald said:
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
Click to expand...
Click to collapse
I don't wanna relock the bootloader. Not sure what to remove from system apps, etc. This was not this difficult the first time I rooted. Thanks for any and all help.
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
dahawthorne said:
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0.0.0?
Disregard, did everything suggested by rmarkwald and dahawthorne. Worked well, took some security update that happened to get rid of the corrupt phone boot message. Flashed twrp 3.0.0.0 and installed SuperSU 2.67 with no problems. Thanks all.
In the process to upgrade to the latest ROM, I had upgraded & installed the latest TWRP 3.2.1 and had downloaded the latest
gapps & lineageos zip files to the Moto X 2014 Phone.
Without thinking clearly, I ran the Advanced WIPE & cleared all the partitions - Dalvik, system, data, storage, cache...
Now, I can boot into TWRP recovery but no files to install.
I have installed ANDROID SDK on my Win 7 (64 bit) laptop.
Have installed MOTO X 2014 USB drivers on my PC from Motorola website.
I have downloaded the LINEAGEOS zip file onto my laptop.
I am trying to transfer files from my PC to Phone.
PC does not recognize the Phone.
$ adb devices ==> does not list any devices
Any help is greatly appreciated.
RYRNRY said:
In the process to upgrade to the latest ROM, I had upgraded & installed the latest TWRP 3.2.1 and had downloaded the latest
gapps & lineageos zip files to the Moto X 2014 Phone.
Without thinking clearly, I ran the Advanced WIPE & cleared all the partitions - Dalvik, system, data, storage, cache...
Now, I can boot into TWRP recovery but no files to install.
I have installed ANDROID SDK on my Win 7 (64 bit) laptop.
Have installed MOTO X 2014 USB drivers on my PC from Motorola website.
I have downloaded the LINEAGEOS zip file onto my laptop.
I am trying to transfer files from my PC to Phone.
PC does not recognize the Phone.
$ adb devices ==> does not list any devices
Any help is greatly appreciated.
Click to expand...
Click to collapse
So the phone doesn't show up under My Computer when it's plugged in? Check Windows Device Manager, is there an "Android" device, try Windows Update while the phone is plugged in; check under USB devices in Device Manager (Composite device or something, you may need to reinstall the drivers manually, they would be under Program Files, Motorola...). It may also be a Windows 7 issue, which I haven't used for years now.
And try both:
adb devices
fastboot devices
It should show your phone's Serial Number. Not sure what else to suggest; you may or may not be able to reflash factory stock firmware, something like this:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
RYRNRY said:
In the process to upgrade to the latest ROM, I had upgraded & installed the latest TWRP 3.2.1 and had downloaded the latest
gapps & lineageos zip files to the Moto X 2014 Phone.
Without thinking clearly, I ran the Advanced WIPE & cleared all the partitions - Dalvik, system, data, storage, cache...
Now, I can boot into TWRP recovery but no files to install.
I have installed ANDROID SDK on my Win 7 (64 bit) laptop.
Have installed MOTO X 2014 USB drivers on my PC from Motorola website.
I have downloaded the LINEAGEOS zip file onto my laptop.
I am trying to transfer files from my PC to Phone.
PC does not recognize the Phone.
$ adb devices ==> does not list any devices
Any help is greatly appreciated.
Click to expand...
Click to collapse
Try it...
https://forum.xda-developers.com/moto-x-2014/general/guide-moto-x2-2014-victara-to-100-one-t3733177
---------- Post added at 10:45 PM ---------- Previous post was at 10:42 PM ----------
2nd option if you are still in TWRP connect your phone with PC while in TWRP and place ROM & Gapps and just flash
Hi, I am stuck in a bootloop with my pixel 4XL and can only access fastboot/adb. I want to pull my photos from the device before wiping it to factory settings but cannot figure out a way to do it. My bootloader is unlocked so figured it was possible somehow.
I cannot access files under sdcard using abd and changing the recovery image doesn't seem to work (I tried TWRP) using fastboot flash recovery, I get this error:
Writing 'recovery' FAILED (remote: 'No such file or directory')
I am guessing TWRP doesn't work because of Android 10
Have I got any options to try and backup my data?
TWRP doesn't work on devices that had Android 10 pre-installed due to a new partition scheme.
I would try dirty flashing a Google stock image of your current build. It should undo any kernel or Magisk changes for booting purposes.
Google images: https://developers.google.com/android/images#coral
Platform Tools: https://developer.android.com/studio/releases/platform-tools.html
Extract the image ZIP somewhere, extract platform-tools into that same folder. (fastboot/adb, the .bat file and the 2nd image-coral*.zip should all be in the same folder)
Edit the "flash-all.bat" file, line 23 should look like this: "fastboot update image-coral-qq2a.200405.005.zip" (remove the '-w' or your photos/data will be wiped!)
Make sure fastboot devices sees the phone, run the .bat and mostly ignore your phone screen until the .bat says it's done.
Dirty flashing may corrupt your face data which might later require a full factory reset. Normally you would delete the face data before dirty flashing.