Database Develop

[Q] I just dun goofed :(

Hey guys, long time lurker and now first time poster. Shame it has to be something very stupid.
So anyways, I wanted to flash the latest CM10.2 Unofficial build so I did the usual and downloaded the zip & gapps to my phone. But upon wiping my phone via TWRP I accidentally left the wipe userdata part checked and ... well now I have no OS installed as well as no zip's :/
I have TWRP installed so I thought why not sideload it, however when I go to advanced -> adb sideload it never starts up. This is the log:
Updating partition details...
Starting ADB sideload feature...
Click to expand...
Click to collapse
And it just stays there
I know that my ADB works as I have S-OFF & unlocked the bootloader and flashed the latest 1.54.0000 hboot so I can definitely use it, I just don't understand why it doesn't let me sideload for some reason.
Either way, I have full access to fastboot & TWRP recovery so i'm hoping this is a pretty simple thing to fix ... right?
Can anybody point me to the right direction?
Details:
No OS installed.
Access to TWRP & fastboot.
S-OFF, Modified Hboot 1.54.0000 (SuperCID) & Unlocked bootloader.
Windows 8 64-bit, drivers all work.
Latest SDK with all the binaries installed.
P.S. when I connect and try and use adb devices it doesn't recognise my device, and the cmd window gives the following when I try the sideload command:
Error: device not found.
Click to expand...
Click to collapse
Sounds like a driver issue to me but it doesn't make sense that the drivers would suddenly stop working ???
Here are screenshots of odd device behaviour when switching from fastboot to recovery (please copy & paste, I don't have enough posts to post images yet):
i.imgur.com/V79DFFA.jpg
i.imgur.com/MKD5C9U.jpg

Bump for help

I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium

redbull123 said:
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Tried that already, same issue in not detecting the device. I'm downloading these drivers in a hope to fix something.
Thanks for the reply
EDIT:
Finally got sideloading in TWRP to work, it turns out it was a driver issue :/
Anyways, these are the drivers that worked:
androidfiles.org/hasoon2000/getdownload.php?file=HTC%20Drivers/HTCDriver.exe

why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..

IINexusII said:
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
Click to expand...
Click to collapse
TWRP is much better for people who know what they are doing. There are more options and also a built in file manager. Also, the wipe button in TWRP wipes the 3 main partitions at once (data/cache/dalvik), so he must have actually selected internal sdcard from the advanced menu, and I have no idea why he would do that...

Doing the slider is all anyone needs to do in twrp to wipe yet I read more posts about people wiping with twrp than any other problem in these forums

[Q] Stuck in Boot Cycle With Other Problems

Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.

XaBuddy said:
Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.
Click to expand...
Click to collapse
fastboot erase cache
then flash the recovery again (twrp 2.6.3.3 suggested)
then from recovery wipe and adb push or sideload the rom

I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?

XaBuddy said:
I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?
Click to expand...
Click to collapse
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
I was ablt to get adb to recognize the phone however it lists it as a host. I go into the twrp and do the sideload but it opens up the debug message. adb sideload os.zip is the command I'm using as I renamed the file to os.zip so i don't have to type so much. I tried the adb push but it says error:Closed.

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory

XaBuddy said:
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory
Click to expand...
Click to collapse
Try this instead
adb push os.zip /sdcard/os.zip

mb_guy said:
Try this instead
adb push os.zip /sdcard/os.zip
Click to expand...
Click to collapse
It worked!! Thank you so much. I had tried adb push os.zip /sdcard/ a while ago but it didn't take. by typing the zip name after sdcard i assume that "gives" the file an exact location to be placed?

[SOLVED] [Q] HTC One only bootloader and recovery works

Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.

OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU

Bruce666 said:
OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU
Click to expand...
Click to collapse
It didn't work Which RUU should i choose? M7-UL, hboot-1.55.0000, radio-4a.21.3263.04. I live in russia so i suppose i need one with "europe" in it's name? And how should i re-lock? Just by using fastboot command?

Give me CID ill try to find ruu 4u

Bruce666 said:
Give me CID ill try to find ruu 4u
Click to expand...
Click to collapse
HTC_A07

http://www.htc1guru.com/2014/03/android-ruu-europe/

Bruce666 said:
http://www.htc1guru.com/2014/03/android-ruu-europe/
Click to expand...
Click to collapse
Thank you very much! Really hope this works.

It must work. If you need help writr here

[email protected] said:
Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.
Click to expand...
Click to collapse
If it reboots immediately when you try to wipe or flash something (i.e instant black screen then reboot)
You can probably fix it with e2fsck.
Boot to recovery select Mount then unmount all partitions return to twrp home screen and connect usb and check adb is working with
Code:
adb devices
You should get an output of your serial no.
Then do this
Code:
adb shell
e2fsck -fvy /dev/block/mmcblk0p35
e2fsck -fvy /dev/block/mmcblk0p36
e2fsck -fvy /dev/block/mmcblk0p37
exit
Now try to flash the Rom again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".

[email protected] said:
After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".
Click to expand...
Click to collapse
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs

nkk71 said:
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs
Click to expand...
Click to collapse
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!

[email protected] said:
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!
Click to expand...
Click to collapse
no problem,
2.6.3.3 is best for most ROMs, unless they require a recovery with "by-name" support (such as CM11), then you need 2.7.0.8 or higher
i've also successfully flashed using 2.8.0.1, but .2 seems to have issues again.
and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

[Q] XT1092 in bootloop after lollipop update

So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.

Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5

All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.

LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!

HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.

purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...

HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.

Ok, cheers. I'll get a usb otg cable and give it a go.

HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.

purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.

purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?

Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!

HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.

Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!

First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.

purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks

Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.

purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.

It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!

Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.

[help] Locked bootloader, and stuck in bootloop with TWRP installed.

So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?

Bigsam411 said:
So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?
Click to expand...
Click to collapse
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.

The_Merovingian said:
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.
Click to expand...
Click to collapse
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
Should show as standard device storage like MTP. Not under adb. Should show as a drive.

The_Merovingian said:
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.
Click to expand...
Click to collapse
My phone shows up in windows Explorer but I cannot move anything over to it. I am in TWRP and cannot see the storage partition.

prdog1 said:
Should show as standard device storage like MTP. Not under adb. Should show as a drive.
Click to expand...
Click to collapse
It does show up but I am unable to transfer anything to it.

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Did you use the fastboot commands?

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Have seen this before. Try unplugging and plug back in. There is some way to access it. Never had to do it.

The_Merovingian said:
Did you use the fastboot commands?
Click to expand...
Click to collapse
I had previously tried those before opening this thread, then I tried them again just now. I attached the output from command prompt.

Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?

Bigsam411 said:
Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?
Click to expand...
Click to collapse
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117

prdog1 said:
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117
Click to expand...
Click to collapse
Thanks, I ended up finding a file that could be flashed via an adb command in twrp which let me issue the fastboot oem unlock command and I then flashed stock through twrp. I think I got it working now.