Database Develop

[GUIDE] Update to Lollipop without losing apps/settings

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 !

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Sorry for my bad english! I hope someone can help me!
Here I put the files I've already uploaded! USE AT YOUR OWN RISK!
https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw
USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER
How-to:
-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder
-Copy the TWRP Backup to your SD Card Backup's folder
Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and
"fastboot flash motoboot motoboot.img")
fastboot flash logo logo.bin <--- From Retail US Firmware
fastboot flash boot boot.img <--- From XT1064 Nextel México
fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link
-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.
-Power Off the Device and enter to Fastboot again.
fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware
fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México
fastboot erase cache
fastboot erase userdata

ejsmsupersoyelm said:
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Click to expand...
Click to collapse
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.

reefuge said:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
Click to expand...
Click to collapse
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...

ejsmsupersoyelm said:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
Click to expand...
Click to collapse
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.
So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.
ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.
Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb
again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.
but i will give you a idea how to do
using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else
rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )
then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.
this is a very simple idea, there are more steps so search for a guide on here

I just need the motoboot.img file, would provide for me?

[Q] Moto G 2014 CM12.1 flashing problem after unlock

Hi folks,
I made a mistake after unlocking my Moto G XT 1068.
After unlocking was confirmed i did not boot it back to system.
Instead I installed TWRP 2.8.5.0 thru fastboot .
Then i rebooted to TWRP.
Inside TWRP i flashed CM12.1 zip. Then got a list of errors (image1).
All errors mention "E:Unable to mount '/data'"
Tried mounting 'data' too but i get a vibrate when i select 'data' partition and it is not selected.
Same while trying to fix data partition or trying to change file system.
How to mount it thru terminal commands in TWRP? Or thru fastboot?
Can anyone help with this please?
I also downloaded the stock firmware for the XT1068 (614 MB size) . Will flashing that work ?
If yes, how to flash that using fastboot? Can i just try to flash that zip thru TWRP?
Kind help required.
regards,
Anoop

anoopgkris said:
Hi folks,
I made a mistake after unlocking my Moto G XT 1068.
After unlocking was confirmed i did not boot it back to system.
Instead I installed TWRP 2.8.5.0 thru fastboot .
Then i rebooted to TWRP.
Inside TWRP i flashed CM12.1 zip. Then got a list of errors (image1).
All errors mention "E:Unable to mount '/data'"
Tried mounting 'data' too but i get a vibrate when i select 'data' partition and it is not selected.
Same while trying to fix data partition or trying to change file system.
How to mount it thru terminal commands in TWRP? Or thru fastboot?
Can anyone help with this please?
I also downloaded the stock firmware for the XT1068 (614 MB size) . Will flashing that work ?
If yes, how to flash that using fastboot? Can i just try to flash that zip thru TWRP?
Kind help required.
regards,
Anoop
Click to expand...
Click to collapse
Try flashing stock with fastboot commands..!?

dj krishna said:
Try flashing stock with fastboot commands..!?
Click to expand...
Click to collapse
Hi,
Do you mean the commands for the partition, boot, system, modem, cache etc? Where can I get the set of commands?
I found one link showing the process using mfastboot. Are they similar?
But can I go ahead without resolving the mount problem? Any idea why that mount problem cropped up?
Sent from my GT-I9001 using XDA Free mobile app

anoopgkris said:
Hi,
Do you mean the commands for the partition, boot, system, modem, cache etc? Where can I get the set of commands?
I found one link showing the process using mfastboot. Are they similar?
But can I go ahead without resolving the mount problem? Any idea why that mount problem cropped up?
Sent from my GT-I9001 using XDA Free mobile app
Click to expand...
Click to collapse
yaa !! download mfastboot zip file extract it into your pc and download stock unzip it, and copy all the files to mfastboot folder which you have extracted
now in that mfastboot folder right click mouse button and hit open command window hear now copy this commands one after the other and make sure you hit enter for every single command
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
and make sure you download the stock firmware not the flashable zip :good:
good luck

SOLVED-Moto G 2014 flash problem
dj krishna said:
yaa !! download mfastboot zip file extract it into your pc and download stock unzip it, and copy all the files to mfastboot folder which you have extracted
now in that mfastboot folder right click mouse button and hit open command window hear now copy this commands one after the other and make sure you hit enter for every single command
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
and make sure you download the stock firmware not the flashable zip :good:
good luck
Click to expand...
Click to collapse
Thanks bro, it worked with textbook precision. Booted back to stock Lollipop.
smitharro said:
Here you can find stock firmwares of all Moto G variants (including the 2013 variants). So br sure to choose the right version!
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
Click to expand...
Click to collapse
Thanks Harro, for the stock links, those worked when none others did . :good:
Will flash CM in some time.

Downgrading from 6.0 to 5.02 using easy installer

I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!

You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.

MobileHD said:
You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.
Click to expand...
Click to collapse
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?

garyben60 said:
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?
Click to expand...
Click to collapse
Just make sure the following files are in the folder where you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!

MobileHD said:
Just make sure the following files are in the folder while you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!
Click to expand...
Click to collapse
Thanks again!! really appreciate your help..

One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?

garyben60 said:
I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!
Click to expand...
Click to collapse
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.

Manav08 said:
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.
Click to expand...
Click to collapse
. Thank you. I saw your video. Well done! I do have a question.. Did you modify the easy installer bat file in any way? The reason I'm asking this because if you read the previous replies certain modifications to the code within the bat file have to be made so that the bootloader doesn't get downgraded thus hardbricking the device.

garyben60 said:
One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?
Click to expand...
Click to collapse
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.

MobileHD said:
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.
Click to expand...
Click to collapse
. Thanks a million for your input.. What are your views about the video?

garyben60 said:
. Thanks a million for your input.. What are your views about the video?
Click to expand...
Click to collapse
I can see in the video that the easyinstaller script used, attempted to flash 'motoboot.img' which you sure avoid doing. What I suggest is to follow the instructions from the video but use my flash script instead.

My thoughts exactly. ..

If anyone uses this method to downgrade don't do what I did and after downgrade allow your device to take any official updates or your device will hard brick. It happened to me and my moto g is now a paperweight.
Sent from my XT1068 using XDA-Developers mobile app

Moto X 2014 - All Partitions WIPED - Bricked - How to Recover

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