Database Info

[Q] Please help problems with rom toolbox theme on my atrix 2

so of course with my noobish self i decide hey im going to fool around with the rom toolbox app and i think hey i wonder what this theme would look like so download and install now my phone is screwed it isnt stuck in a bootloop or bricked but now i cant do really anything without it making my phone force close or it rebooting completely it will let my get in the app but not under the theme section which is where i would have to go to restore my settings is there any advice xda can give me because i just cant seem to find an answer
p.s never using rom toolbox themes again

espeyboi said:
so of course with my noobish self i decide hey im going to fool around with the rom toolbox app and i think hey i wonder what this theme would look like so download and install now my phone is screwed it isnt stuck in a bootloop or bricked but now i cant do really anything without it making my phone force close or it rebooting completely it will let my get in the app but not under the theme section which is where i would have to go to restore my settings is there any advice xda can give me because i just cant seem to find an answer
p.s never using rom toolbox themes again
Click to expand...
Click to collapse
I believe Rom Toolbox isn't good for much, if anything. I'm not sure why changing or downloading themes in this app could cause you to bootloop, but if it has you need to run a 'return to stock' 2.3.5 script by booting into AP Fastboot or use RSD Lite. OTA update to 2.3.6, re-root, and you should be good.
Everything you need to know is found here: http://forum.xda-developers.com/showthread.php?t=1396650
Also, going forward, ALWAYS make a CWM Backup before doing anything, like flashing roms or experimenting with root apps.
Sent from my MB865 using xda premium

so i tryed that and now my phone wont work pretty much at all its stuck in a loop to where it will load up and after about 5 seconds not even enough time to have it usb connected to my computer to add or delete anything it keeps saying google process stopped and all these other processes stopped then it starts over again i just got the phone less than two months ago i really need help with this any advice???

There is no reason why the aforementioned suggestion shouldn't have worked. Couple things to keep in mind:
Do you have a fully charged battery when doing all this?
Do you have the Motorola USB drivers installed?
Did you DL the proper fxz for your phone?
Make sure you boot into fast boot by holding up on the volume rocker, and then holding the power button down.
Attach your USB cable to the BACK of your com, and follow the instructions listed out in the link in the post above.
Follow them exactly!
Once again, here's the link. http://forum.xda-developers.com/showthread.php?t=1396650
Sent from my MB865 using xda premium

Fall of Enosis said:
There is no reason why the aforementioned suggestion shouldn't have worked. Couple things to keep in mind:
Do you have a fully charged battery when doing all this?
Do you have the Motorola USB drivers installed?
Did you DL the proper fxz for your phone?
Make sure you boot into fast boot by holding up on the volume rocker, and then holding the power button down.
Attach your USB cable to the BACK of your com, and follow the instructions listed out in the link in the post above.
Follow them exactly!
Once again, here's the link. http://forum.xda-developers.com/showthread.php?t=1396650
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
So i get ready to do all that and neither of the files are working for me to be able to download the 2.3.5 do any of you have another link i could use because i cant find one and also i dont know if it is suppose to do this when i put it into fastboot after like a minute it starts to load up and wont stay into fastboot
thanks for your patience

espeyboi said:
So i get ready to do all that and neither of the files are working for me to be able to download the 2.3.5 do any of you have another link i could use because i cant find one and also i dont know if it is suppose to do this when i put it into fastboot after like a minute it starts to load up and wont stay into fastboot
thanks for your patience
Click to expand...
Click to collapse
Before using the restore script you need to install the USB drivers for your MB865 (If this your model A2), you can get those from HERE:
Next, unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ ) The script can be downloaded HERE:
Then, connect your phone with the USB cable to the PC and get into FastBoot mode for this in your phone by pressing and holding down the volume down & volume up & power at the same time. It should appear with a screen and some options; use the volume down key of your phone to navigate through the menu until you see the AP FastBoot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said USB connected.
Then open the folder where you extracted the Return to Stock 2.3.5 FastBoot SCRIPT files and search a .bat file call "Stock Restore" - should be toward the bottom of the files in this folder. Then run the file (double click on it) and it should open a command prompt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the ID of your device and it will wait you to press the enter key to start the process. Press any key to enter and wait for the process to begin to program. Then, after some time the command prompt window will give you a message saying its finished. After that, it will reboot your phone and install the stock 2.3.5. When it boots up again, you should see the android logo and a progress bar filling up.
When it's done wait for the device to reboot again, and after that you can OTA (Over-The-Air) update to Android version 2.3.6. by navigating in your device to Settings/About Phone/System Updates.
Hope this helps.
(Thanks to jfrank1485!)

This link should still be good: http://www.filefactory.com/file/2zx...hing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
This assuming you are using a AT&T MB865 model. Verify before you flash!
Here's the original thread: http://forum.xda-developers.com/archive/index.php/t-1415336.html
Sent from my MB865 using xda premium

Apex_Strider said:
Before using the restore script you need to install the USB drivers for your MB865 (If this your model A2), you can get those from HERE:
Next, unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ ) The script can be downloaded HERE:
Then, connect your phone with the USB cable to the PC and get into FastBoot mode for this in your phone by pressing and holding down the volume down & volume up & power at the same time. It should appear with a screen and some options; use the volume down key of your phone to navigate through the menu until you see the AP FastBoot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said USB connected.
Then open the folder where you extracted the Return to Stock 2.3.5 FastBoot SCRIPT files and search a .bat file call "Stock Restore" - should be toward the bottom of the files in this folder. Then run the file (double click on it) and it should open a command prompt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the ID of your device and it will wait you to press the enter key to start the process. Press any key to enter and wait for the process to begin to program. Then, after some time the command prompt window will give you a message saying its finished. After that, it will reboot your phone and install the stock 2.3.5. When it boots up again, you should see the android logo and a progress bar filling up.
When it's done wait for the device to reboot again, and after that you can OTA (Over-The-Air) update to Android version 2.3.6. by navigating in your device to Settings/About Phone/System Updates.
Hope this helps.
(Thanks to jfrank1485!)
Click to expand...
Click to collapse
you are the best i got it all figured out many many thanks

espeyboi said:
you are the best i got it all figured out many many thanks
Click to expand...
Click to collapse
Good to hear you're back in business! FYI: remember this process, as you may need it again for future reference!
Sent from my MB865 using xda premium

Apex_Strider said:
Good to hear you're back in business! FYI: remember this process, as you may need it again for future reference!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
so true. My record is 29 softbricks in one day.

Also, install CWM on boot!
This way your phone ALWAYS boots into recovery on initial start up. Saved me too many times to count.
See here: http://forum.xda-developers.com/showthread.php?t=1606257
Or certain roms already have it.
Sent from my MB865 using xda premium

Fall of Enosis said:
Also, install CWM on boot!
This way your phone ALWAYS boots into recovery on initial start up. Saved me too many times to count.
See here: http://forum.xda-developers.com/showthread.php?t=1606257
Or certain roms already have it.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
+1 CWM on boot
Sent from my MB865 using xda premium

I don't have time to get into development yet, and I still make sure I put that on...just a lifesaver if something goes wrong!

Build.prop

I have the Motorola Fire XT rooted and deleted the build.prop file in the system. I have a back - up of the file on my computer but not my phone. I need to figure out a way how to put it on my phone. My phone is in a boot loop. Any help? Thanks.

You could push it to your device via adb. This can be done manually or you could use a tool such as this: http://forum.xda-developers.com/showthread.php?t=1599332.

You need adb. Install adb and put the build.prop file in the same folder as adb and use the command "adb push build.prop /system"

Theonew said:
You could push it to your device via adb. This can be done manually or you could use a tool such as this: http://forum.xda-developers.com/showthread.php?t=1599332.
Click to expand...
Click to collapse
estallings15 said:
You need adb. Install adb and put the build.prop file in the same folder as adb and use the command "adb push build.prop /system"
Click to expand...
Click to collapse
What can one do if this action is needed (running ADB) but the user haven't turned on USB-Debuggning, nor can enter the recovery mode.
Considered a bricked device?

nikkop said:
What can one do if this action is needed (running ADB) but the user haven't turned on USB-Debuggning, nor can enter the recovery mode.
Considered a bricked device?
Click to expand...
Click to collapse
No. Do you have this issue? If so, are you able to boot into fastboot/bootloader?

Theonew said:
No. Do you have this issue? If so, are you able to boot into fastboot/bootloader?
Click to expand...
Click to collapse
Hello,
Yes I do.
I can't get into recovery mode because the device gets stuck at the logo.
I know it's the correct buttons being pressed as I do have another same tablet which enters recovery without problems.
If you mean fastboot via USB-Debugging? Well I can't do any ADB because I don't have USB-debugging enabled.
Any idea how to rescue this tab?
Thanks

nikkop said:
Hello,
Yes I do.
I can't get into recovery mode because the device gets stuck at the logo.
I know it's the correct buttons being pressed as I do have another same tablet which enters recovery without problems.
If you mean fastboot via USB-Debugging? Well I can't do any ADB because I don't have USB-debugging enabled.
Any idea how to rescue this tab?
Thanks
Click to expand...
Click to collapse
If resetting the device doesn't work, you don't have access to recovery mode/bootloader/fastboot or even download mode (depending on your device), then there is pretty much nothing you can really do to fix it yourself. The only other possibility would be to try to run the stock ruu (if it has one).

Theonew said:
If resetting the device doesn't work, you don't have access to recovery mode/bootloader/fastboot or even download mode (depending on your device), then there is pretty much nothing you can really do to fix it yourself. The only other possibility would be to try to run the stock ruu (if it has one).
Click to expand...
Click to collapse
Thanks for the suggestions, but that would suck
Must be something I can do.
It's a Chinese brand tablet, the quality is good but this is the only issue.
However, if I plug in the tablet to the computer, something called "WinDroid Linker" shows up on the PC and I remote to the tablet while I'm on the screen that says I need to do a factory reset. From there I can reach keyboard settings, but that's all I've figured out so far.
Due to the fact that I'm able to remote the tablet, shouldn't I be able to do something from there?
I'm not, however, able to reach the storage as far as I know.
Thanks

nikkop said:
Thanks for the suggestions, but that would suck
Must be something I can do.
It's a Chinese brand tablet, the quality is good but this is the only issue.
However, if I plug in the tablet to the computer, something called "WinDroid Linker" shows up on the PC and I remote to the tablet while I'm on the screen that says I need to do a factory reset. From there I can reach keyboard settings, but that's all I've figured out so far.
Due to the fact that I'm able to remote the tablet, shouldn't I be able to do something from there?
I'm not, however, able to reach the storage as far as I know.
Thanks
Click to expand...
Click to collapse
Maybe, but only if you can bypass the part.

Thanks
Thanks for all the suggestions. I have already tried adb but it says my phone is offline. I can get into recovery but idk if that will do much. Idk how to get my phone into fastboot. Thanks.

Theonew said:
If resetting the device doesn't work, you don't have access to recovery mode/bootloader/fastboot or even download mode (depending on your device), then there is pretty much nothing you can really do to fix it yourself. The only other possibility would be to try to run the stock ruu (if it has one).
Click to expand...
Click to collapse
I can get into recovery mode but ADB says my phone is offline so I cant do anything with that. Idk what bootloader is or fast boot but maybe that would be a solution. Thanks.

If you can get into recovery mode, find the mount options. Mount /system. Then adb push the file to your phone.
Sent from my SGH-T999 using xda premium

Theonew said:
If resetting the device doesn't work, you don't have access to recovery mode/bootloader/fastboot or even download mode (depending on your device), then there is pretty much nothing you can really do to fix it yourself. The only other possibility would be to try to run the stock ruu (if it has one).
Click to expand...
Click to collapse
option94 said:
If you can get into recovery mode, find the mount options. Mount /system. Then adb push the file to your phone.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Ya but if im in recovery my phone wont show up in the listed devices. And now my device wont show up as its booting up. If there is a way for adb to recognize the phone in recovery that would be great.

If you have adb properly setup it should see it in recovery. What recovery are youbusing? I do this stuff in clockwork all the time when I'm porting roms.
Sent from my SGH-T999 using xda premium

option94 said:
If you have adb properly setup it should see it in recovery. What recovery are youbusing? I do this stuff in clockwork all the time when I'm porting roms.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Android system recovery. Idk how to get clockwork.

Froggywoggy25 said:
Android system recovery. Idk how to get clockwork.
Click to expand...
Click to collapse
See my post about unbricking fire xt.
Don't forget the Thanks button
Sent from my XT530 using xda app-developers app

build.prop lost
can u put a copy of build.prop becoz i hav lost my copy......

aweosomeabhijeet said:
See my post about unbricking fire xt.
Don't forget the Thanks button
Sent from my XT530 using xda app-developers app
Click to expand...
Click to collapse
can u post build.prop for motorola fire xt 530......

[Q] Htc One S Black screen Brick

Hello... I was using CM nightly then i wanted to overclock my phone so i flashed this http://forum.xda-developers.com/showthread.php?t=2061577 Then everything was working fine but i wasnt able to enable the Wi-Fi it was grayed out on disabled.Then i wanted to fix it so i flashed another kernel(i will post what kernel about tomorrow it probably is for ICS)(yes im a noob i realised that later with an awesome facepalm)so... now im stuck in a black screen and i cannot hear anything from my phone. i cant boot it into bootloader and/or TWRP recovery there is only a black screen i can see that it works cuz if i have it connected on my laptop the laptop makes the USB connection sound and/or disconnection one so it is probably working (i tryed holding the power button for 10 and then VOL down to put it on bootloader after the 10 sec's my laptop made a sound but i wasnt able to make it work...) so im stuck here.
P.S.:I would really apriciate your help.Sorry for F*cking English Grammar
Thanasis,15,Greece.

man, you need to reduce your font
and you flashed a kernel for the one x
sorry about your situation, but you are going to have to read more stuff and more carefully
this happened to someone else forget solution if any
try a google on flashing one x kernel on a one s, unless someone replies soon
---------- Post added at 08:03 PM ---------- Previous post was at 07:57 PM ----------
btw i never saw much advantage to overclocking for me anyway
if you get this sorted, i would stay with stock kernels for now. have a nandroid and sdcard bu on pc.
i prefer twrp recovery, but not the latest one as it has issues
read all OP pages very carefully and i read first/last 20 pages or so of the thread
always include System as part of your full wipes
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
also, hold vol- then pwr at same time until the soft keys blink 3 times. release pwr but continue holding vol-
hold it down til phone boots--give it a minute
you can try using adb if you have that set up on pc

rugmankc said:
man, you need to reduce your font
and you flashed a kernel for the one x
sorry about your situation, but you are going to have to read more stuff and more carefully
this happened to someone else forget solution if any
try a google on flashing one x kernel on a one s, unless someone replies soon
---------- Post added at 08:03 PM ---------- Previous post was at 07:57 PM ----------
btw i never saw much advantage to overclocking for me anyway
if you get this sorted, i would stay with stock kernels for now. have a nandroid and sdcard bu on pc.
i prefer twrp recovery, but not the latest one as it has issues
read all OP pages very carefully and i read first/last 20 pages or so of the thread
always include System as part of your full wipes
---------- Post added at 08:08 PM ---------- Previous post was at 08:03 PM ----------
also, hold vol- then pwr at same time until the soft keys blink 3 times. release pwr but continue holding vol-
hold it down til phone boots--give it a minute
you can try using adb if you have that set up on pc
Click to expand...
Click to collapse
will do/try all of your tip's
about the vol- and then pwr... this just doesnt work cuz the second kernel i flashed was for ICS and they wont light up if they were lightning up it would be easy cuz i cound access bootloader and then all fixed :crying:

Sorry OP, but it sounds like you're bricked. You see QHSUSB_DLOAD when you connect your phone to the PC? You flashed a One X kernel, which is probably why.
You can try the steps in the development unbricking thread.

yeah, don't sound good
you didn't say is you know how to use adb from a command window on pc
you could try rebooting bootloader from there as a try before unbricking
or go the jtag route

well i tryed accessing adb even when unbricken but couldn't manage to make it work... (tryed enabling it from developer options&usb mode) i read somewhere that JB 4.2.2 has an extra security level and it wont be supported by cyanogenmod 10.1

you don't access it you need to have htc drivers on phone and install the adb and fastboot files onto your pc. put hem in a folder of your choice with only them there.
you then open a command window on pc and cd to that folder and type "adb reboot bootloader" with no quotes
if you meant that, sorry i misunderstood
most people install the android sdk if they plan on doing a lot of adb/fastboot commands

So im stuck?
So im stuck? i cant do anything else i mean i cant get into the partitions and edit'em... probably not so my phone is over had it less than a month :crying:

xakersas said:
well i tryed accessing adb even when unbricken but couldn't manage to make it work... (tryed enabling it from developer options&usb mode) i read somewhere that JB 4.2.2 has an extra security level and it wont be supported by cyanogenmod 10.1
Click to expand...
Click to collapse
Wait, how did you even manage to et into developer options if you're bricked??
Sent from my One S using Tapatalk 2

usaff22 said:
Wait, how did you even manage to et into developer options if you're bricked??
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
no i got in there before bricking the device

xakersas said:
no i got in there before bricking the device
Click to expand...
Click to collapse
OK then. Have you tried the unbricking thread in the Android Development forum?
Some of the steps you don't need, since you are already bricked.
Sent from my One S using Tapatalk 2

here is the second kernel i installed (it is a donwload link couldn't retrive the download page i got this from google sync) http://www.mediafire.com/?acu5fiil0c4o0gu

usaff22 said:
Sorry OP, but it sounds like you're bricked. You see QHSUSB_DLOAD when you connect your phone to the PC? You flashed a One X kernel, which is probably why.
You can try the steps in the development unbricking thread.
Click to expand...
Click to collapse
hello im back yes i can see QHSUSB_DLOAD what can i do?
Edit: i see i got at the unbrick thread but stuck at step step 4 (Enumerating) i dont know which one is my phone's

xakersas said:
here is the second kernel i installed (it is a donwload link couldn't retrive the download page i got this from google sync) http://www.mediafire.com/?acu5fiil0c4o0gu
Click to expand...
Click to collapse
Yes. You flashed an unknown kernel, which just says CM10.1 nightly without reading what devices the kernel is for! It would be a good idea to check if it is for the One S, or Ville, since CM10.1 is available for more than 20 devices!
xakersas said:
hello im back yes i can see QHSUSB_DLOAD what can i do?
Click to expand...
Click to collapse
You shouldn't be smiling too much, you have a bricked device
You will have to try and recover your device using the thread below. You can skip the "creating the brick" section, since you already have a brick. DO NOT USE THE UNLIMITED.IO tool to reset the phone, since it will not work and make the situation worse.
http://forum.xda-developers.com/showthread.php?t=1990043

adb problems

My Nexus 5 is showing up in Device manage as Google Nexus ADB Interface. Has updated drivers. Yet when I open cmd and enter adb devices it's not showing up. This was alreday set up before, and I've used it with no issues, now today nothing.
Please help

Reboot your phone and try
Sent from my Nexus 5

ok. In fastboot mode nothing shows up. However when I go into recovery mode it does. I'm running trinity kernel trying to get into fastboot to go back to stock.

richport29 said:
ok. In fastboot mode nothing shows up. However when I go into recovery mode it does. I'm running trinity kernel trying to get into fastboot to go back to stock.
Click to expand...
Click to collapse
That makes perfect sense. In fastboot use fastboot devices. Or do you mean even using fastboot commands it doesn't recognize the device. I had the opposite problem before where fastboot would work and adb wouldn't. I had to reinstall drivers. Google naked usb drivers and try those.
Sent from my Nexus 5

jd1639 said:
That makes perfect sense. In fastboot use fastboot devices. Or do you mean even using fastboot commands it doesn't recognize the device. I had the opposite problem before where fastboot would work and adb wouldn't. I had to reinstall drivers. Google naked usb drivers and try those.
Sent from my Nexus 5
Click to expand...
Click to collapse
Wow, I feel so dumb right now. Thanks for the help
Working fine now, using the proper commands.

richport29 said:
Wow, I feel so dumb right now. Thanks for the help
Working fine now, using the proper commands.
Click to expand...
Click to collapse
no problem, I've done it before too.
Sent from my Nexus 5

Pull storage from damaged device

So I accidentally dropped my nexus 5 and I need to replace my display but unfortunately I haven't backed up my data (mostly pictures I'm worrying about the most). So is there a way to pull the storage from it? I've tried with adb and it doesn't work because it doesn't list my device.
I really hope there is a way to do it.

If USB works and its not detecting adb, then its set up wrong. Adb is the only way if both touch and display are broken.
Please click the link in my signature and read the adb and fastboot thread. It will tell you how to set it up properly
Sent from my Nexus 5 using Tapatalk

Does it matter if I had an unlock code for my lockscreen?

dndwanted said:
Does it matter if I had an unlock code for my lockscreen?
Click to expand...
Click to collapse
Yes it does.
Don't suppose you have a custom recovery do you?
Sent from my Nexus 5 using Tapatalk

My phone was rooted and I had latest TWRP with latest Paranoid Android,

dndwanted said:
My phone was rooted and I had latest TWRP with latest Paranoid Android,
Click to expand...
Click to collapse
Adb in recovery then. See the thread i previously told you about
Sent from my Nexus 5 using Tapatalk

I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?

dndwanted said:
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
Click to expand...
Click to collapse
You've not read my thread properly. Try again
Sent from my Nexus 5 using Tapatalk

I installed the adb in 15 seconds thing and then I followed this thread http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please tell me what have I done wrong because I can't seem to figure it out.

Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.

@rootSU
I get this: http://imgur.com/ccw4lJ6
:/

ChickenNugget said:
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
Click to expand...
Click to collapse
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately I get the same error.

dndwanted said:
Unfortunately I get the same error.
Click to expand...
Click to collapse
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk

rootSU said:
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://imgur.com/KCoHxg8

dndwanted said:
http://imgur.com/KCoHxg8
Click to expand...
Click to collapse
Unless you can get recovery to show up, you're screwed.
I don't know anything about twrp so I can't help there.
Sent from my Nexus 5 using Tapatalk

Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways

dndwanted said:
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
Click to expand...
Click to collapse
Try manually option 2
Otherwise you can fastboot flash philz recovery - which is a recovery I know.
Sent from my Nexus 5 using Tapatalk

Doesn't work.

dndwanted said:
Doesn't work.
Click to expand...
Click to collapse
In more descriptive terms please
Sent from my Nexus 5 using Tapatalk