ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
i havent had this happen but i know some have im sure someon can help but till then you might want to hit up firewater team on irc #firewater
You're not using a Windows 8.1 PC or a USB 3.0 port, are you?
Mike02z said:
You're not using a Windows 8.1 PC or a USB 3.0 port, are you?
Click to expand...
Click to collapse
For what it's worth I did use a 3.0 port on a z87 board with 8.1 64bit installed with no issues to report. It completed on the first bottle.
Ditto. I used Windows 8.1 and a usb 3 port (is all my laptop has), and everything worked fine - 1st try.
I know that doesn't help op, but would also hate to see him chasing extraneous things that aren't the problem.
slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
I had this problem. I simply rebooted and redid firewater and it went thru. I also wasn't using a pc, just term emulator from within the phone
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Same thing happened to me. Gotta make sure your also using the most current version of adb.
Sent from my HTC6525LVW using xda app-developers app
Also make sure your screen is awake and doesnt have any type of lock screen. I just had slide to unlock and it didnt work first time, disabled it and made sure screen never went to sleep and worked 2nd time no issues.
slide83 said:
ADB sees my phone, everything is getting pushed to the phone and when I run firewater, it goes through all 12 bottles and then says it can't complete. Anyone else have this problem? Any ideas?
Click to expand...
Click to collapse
Also did you be sure to chmod firewater after you pushed it
Sent from my HTC6525LVW using XDA Premium 4 mobile app
izzaeroth said:
Also did you be sure to chmod firewater after you pushed it
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this. this is key
Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.
Mine was blinking and I didn't uncheck fastboot
Sent from my HTC6525LVW using XDA Premium 4 mobile app
are you guys watching the video
http://forum.xda-developers.com/showthread.php?t=2697957
jmcamz2899 said:
Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.
Click to expand...
Click to collapse
Got it working. I closed my cmd session. Rebooted phone manually. Waited for root achieved and started over. Only this time I skipped the adb reboot step. All is good now. Also used usb 3.0
Sent from my HTC6525LVW using xda app-developers app
Tried a different USB port, new version of ADB from the how-to video, waiting till root achieved, still goes through all the "bottles" and can't acheive s-off....
I love that most all developers are alcoholics
Any other ideas?
slide83 said:
Any other ideas?
Click to expand...
Click to collapse
Try the adb shell commands directly in terminal emulator
Sent from my HTC6525LVW using XDA Premium 4 mobile app
jmcamz2899 said:
Cant get mine to work either. After adb reboot command, phone reboots and i wait for the "root achved" message and enter adb wait-for-device push firewater/data/local/tmp and cursor goes to next line and just blinks.
Click to expand...
Click to collapse
Mine did the same thing. Adb wasn't recognizing me phone after adb reboot so I unplugged it and plugged it back in. Entered adb devices to makes sure I could see my device and then instead of typing
adb wait-for-device push firewater/data/local/tmp
I typed
adb push firewater/data/local/tmp
And everything went through fine.
Sent from my HTC6525LVW using Tapatalk
can anyone help
Yes
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
Related
I recently tried to root my xoom and got to the point where I need to flash the images. The already mounted USB storage space was not big enough for me to copy the files over (only 3mb and I needed at least 5mb), so I reset the xoom.
It doesn't respond to Power + Vol Up, Vol Down, or any of the above combinations. The only response I get is the charging light when its charging.
What else can I try before attempting to send this in?
Any help is appreciated.
Any luck on getting up and running? I would say try it unplugged, try it with the USB in, and try to wee if its caught somewhere in the boot process by running ddms or seeing if yu can adb reboot....but it would be helpful to explain your exact steps you took to attempt to get root. Did you have a custom recovery image or were you in fastboot when it jacked up?
Sent from my Xoom using Tapatalk
dhemke17 said:
Any luck on getting up and running? I would say try it unplugged, try it with the USB in, and try to wee if its caught somewhere in the boot process by running ddms or seeing if yu can adb reboot....but it would be helpful to explain your exact steps you took to attempt to get root. Did you have a custom recovery image or were you in fastboot when it jacked up?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
No luck at all. I've tried it with USB in, plugged/unplugged. I was in CWR while I had the USB storage from my Xoom mounted, but like I mentioned earlier it only gave me 3mb of space. I used the procedure on this post http://forum.xda-developers.com/showthread.php?t=1083739 It messed up after i flashed CWR and was about to flash the kernals
Make yourself a factory cable, or cough up 50 bucks for one... people posting results with those.
Unless there's another place for me to buy them besides TBH, I guess I can try to make one.
Anyone know of reliable sellers on eBay?
Sent from my DROID2 using XDA App
had same problem i let the battery run down took it back to Bestbuy said it would boot up how long you had it one other thing if you plug it in and do a adb devices does your computer see it cause i can walk you thru that own a couple of units and if you dondt know adb yet i can help with that
A little more than a month ago from my local Verizon store.
Really trying to get this fixed before I deploy
Sent from my DROID2 using XDA App
on the comp question plug it in and bring up your adb and see if the comp sees it dos or shell depending what you on you can push a file while it is asleep
Tried that, adb devices doesn't see it
Sent from my DROID2 using XDA App
dont take poor on your command promp are you in the folder of your platform tools and is sdk up and running what OS are you on
also
http://forum.xda-developers.com/showthread.php?t=970665
same across just to give you more info on the volume up holding power for a bit
fellow floridian to bad your far from me i love went things dont work and fixing them
SDK is up, I was in my tools folder. On Windows 7.
And I'm not even in the state right yet, only get to visit when the Army says I can haha.
Sent from my DROID2 using XDA App
I was trying to root my at&t htc one x from designgears but after the phone restarted twice and the process was complete, my phone became worthless, the homescreen is gone as well as everything except the notification bar. I tried hard reset but when the settings wont open and the volume down button/power button method doesnt do anything but restart my phone to the current worthless state. Need help!!!! How can I fix this problem????
Sounds like the local.prop file was not removed which is causing the instability either run the script again or if you know how to use adb try these commands
adb shell rm /data/local.prop
adb reboot
Sent from my Nocturnalized Beast
I dont know how to use adb
jbarajas19 said:
I dont know how to use adb
Click to expand...
Click to collapse
That's what google is for!
Just download an RUU connect phone to your pc...run RUU.. Let it do its thing... Then leave it stock.
Sent from my HTC One X using xda premium
Alright, this is an interesting one for y'all. Broke my power button on my Sensation about 6 months ago, and have been turning it on using adb on my computer...Well, my computer went kaput this weekend, and my phone decided to freeze as well. Now I can't get it to reboot on any other machine. I'm assuming this may be due to missing HTC drivers, but with the phone off I can't really tell.. adb will only come back with "device not found".
TLR
1) broke power button months ago and boot from adb
2) computer broke, and phone turned off
3) adb on other computers cannot boot phone "device not found"
Any help would be greatly appreciated, spent a few hours playing around with this and no luck yet >.<
ground_sniper said:
Alright, this is an interesting one for y'all. Broke my power button on my Sensation about 6 months ago, and have been turning it on using adb on my computer...Well, my computer went kaput this weekend, and my phone decided to freeze as well. Now I can't get it to reboot on any other machine. I'm assuming this may be due to missing HTC drivers, but with the phone off I can't really tell.. adb will only come back with "device not found".
TLR
1) broke power button months ago and boot from adb
2) computer broke, and phone turned off
3) adb on other computers cannot boot phone "device not found"
Any help would be greatly appreciated, spent a few hours playing around with this and no luck yet >.<
Click to expand...
Click to collapse
Hi,
You are not in a good place,are you?
Drivers are HERE
Try different USB slots.
No USB 3.0 , or hubs.
Still no luck. Thanks, though. Any other ideas?
How did you break the power button? Just the plastic?
Might be easier to fix the button itself than to continue using your gimped device
Might sound stupid.. But did you have usb debugging enabled? (settings- develop options)
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Might sound stupid.. But did you have usb debugging enabled? (settings- develop options)
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
This is critical and easy to overlook. But if thats not the problem try killing and restarting the adb server.
Adb kill-server
Adb start-server
Adb devices
If you are using Linux, run those commands as root
Sudo adb kill-server ......etc etc etc
On more than one occasion that has solved this problem for me
Sent from my HTC Sensation using xda app-developers app
I also think that fixing the button is easiest way. You can remove Sensation cover and make conntact even without button. Later, make sure you do not need to do it again (keep battery charged before phone powers off)
Sent from my HTC Sensation Z710e
Hey everyone! I've been taking help from you people at XDA for quite a while and I never needed to make an account before this.
First off, I would like to thank everyone at the website who contributes in any way. You guys make things a lot easier. :good:
I have a Nexus 5 and I wasn't very fortunate at one of my previous football matches. The screen broke and came off. My lockscreen has a pattern which is causing all the trouble. I want to get my files back from my phone but I don't know how. My phone is rooted and running stock, I do have a custom recovery and I've backed up my ROM. Everything is working perfectly on the phone, I was getting calls, its buzzing from notifications and the notification light is still blinking. I connected it to a PC and it shows but I can't access my data as the screen is locked. Due to some problems with windows 8.1 I turned USB debugging off as my phone wasn't being detected. I have android device manager activated but my WiFi was off when the screen broke so I cant disable the lock.
SUMMARY:
Rooted Nexus 5 running stock android with custom recovery (cwm)
USB debugging may be on/ may not be
Phone working perfectly, just no screen.
WiFi is off.
I have experience with bricked phones, flashing ROMS and stuff.
I just wanted help on how I could get my stuff back. Right now services with which I can control my phone from my PC seem like a very good idea but I can't install an APK on my phone. Please help me out guys. Also, if there are any threads which have solved this problem please link them below. I'm busy trying to get into a university.
EDIT: USB debugging MIGHT be on as I don't perfectly remember turning it off.
Boot in to recovery and then from a command window on your pc try
adb pull /sdcard c:\nexus5
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot in to recovery and then from a command window on your pc try
adb pull /sdcard c:\nexus5
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It says command adb not recognized. I don't have android SDK installed on my laptop.
whynotRaza said:
It says command adb not recognized. I don't have android SDK installed on my laptop.
Click to expand...
Click to collapse
Google 15 second adb drivers xda. That'll set it up for you.
Edit, here's the link http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Nexus 5 using XDA Free mobile app
jd, nice to see your still helping out.
OP, after you get the drivers and/or sdk set up simply type:
Code:
adb devices
If you see a serial number your good. Proceed to pull the entire sdcard.
If you don't see the serial number look up everything you can related to your OS and adb.
Section 5.4 in my signature
Sent from my Nexus 5 using Tapatalk
jd1639 said:
Google 15 second adb drivers xda. That'll set it up for you.
Edit, here's the link http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so much for this! I never bothered with the android SDK as I couldn't install it the first time and I didn't really need it until now. The only problem occurring right now is that I can't turn off my phone, and so I can't boot into recovery. Posting a pic of my phone lol.
rootSU said:
Section 5.4 in my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot! This helped me understand my problem much better. I just can't boot into recovery mode.
whynotRaza said:
Thank you so much for this! I never bothered with the android SDK as I couldn't install it the first time and I didn't really need it until now. The only problem occurring right now is that I can't turn off my phone, and so I can't boot into recovery. Posting a pic of my phone lol.
Thanks a lot! This helped me understand my problem much better. I just can't boot into recovery mode.
Here's my phone:
<iframe src="//instagram.com/p/pxFT15OC53/embed/" width="612" height="710" frameborder="0" scrolling="no" allowtransparency="true"></iframe>
Click to expand...
Click to collapse
With that screen, how would you know if you've entered recovery mode?? I don't know. Can you see anything on the screen?
vin4yak said:
With that screen, how would you know if you've entered recovery mode?? I don't know. Can you see anything on the screen?
Click to expand...
Click to collapse
I should have posted a better pic. The screen isn't connected anymore, it came off completely. I can't see anything on it at all.
after setting up adb on pc and running it wouldnt the command "adb reboot recovery" take him to the recovery section? then he can run the command "adb pull"
vin4yak said:
With that screen, how would you know if you've entered recovery mode?? I don't know. Can you see anything on the screen?
Click to expand...
Click to collapse
Ensure device is off
Hold vol down + Power until you feel vibration
Press vol up twice
Press power (Will feel another vibration)
Connect USB
run adb devices should see something like:
Code:
H:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
03105ef70935976465 [B][COLOR="Red"]recovery[/COLOR][/B]
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
kunaltyagii said:
after setting up adb on pc and running it wouldnt the command "adb reboot recovery" take him to the recovery section? then he can run the command "adb pull"
Click to expand...
Click to collapse
Maybe, ROM settings / USB debugging / Root dependent potentially though
whynotRaza said:
I should have posted a better pic. The screen isn't connected anymore, it came off completely. I can't see anything on it at all.
Click to expand...
Click to collapse
How do you know whether the phone is turned on or not? Notification sounds work? Try what @kunaltyagii suggested.
kunaltyagii said:
after setting up adb on pc and running it wouldnt the command "adb reboot recovery" take him to the recovery section? then he can run the command "adb pull"
Click to expand...
Click to collapse
Yes it will. That's an excellent idea as long he has USB debugging enabled. :good:
---------- Post added at 05:42 PM ---------- Previous post was at 05:16 PM ----------
rootSU said:
Ensure device is off
Hold vol down + Power until you feel vibration
Press vol up twice
Press power (Will feel another vibration)
Click to expand...
Click to collapse
Oh yeah! Good one. Didn't strike me.
theesotericone said:
jd, nice to see your still helping out.
OP, after you get the drivers and/or sdk set up simply type:
Code:
adb devices
If you see a serial number your good. Proceed to pull the entire sdcard.
If you don't see the serial number look up everything you can related to your OS and adb.
Click to expand...
Click to collapse
Yep, still around. You still have the rocket?
Sent from my Nexus 5 using XDA Free mobile app
rootSU said:
Ensure device is off
Hold vol down + Power until you feel vibration
Press vol up twice
Press power (Will feel another vibration)
Connect USB
run adb devices should see something like:
Code:
H:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
03105ef70935976465 [B][COLOR="Red"]recovery[/COLOR][/B]
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Maybe, ROM settings / USB debugging / Root dependent potentially though
Click to expand...
Click to collapse
Thanks a bunch! I dont think my hardware keys are working properly. I turned my phone off by disconencting the battery conenctions. I tried booting into recovery but my phone turned on normally instead. I tried "adb devices" and luckily it showed my serial number followed by "device". I just randomly tried "adb pull sdcard/music" and it worked! So now I have access to all my files. Could you guys post some links to advanced push and pull commands? I dont want to pull everything, I want my folder trees so that I can only take out the important stuff.
jd1639 said:
Google 15 second adb drivers xda. That'll set it up for you.
Edit, here's the link http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again! I wouldn't have gotten anywhere without this!
New problem: I did all that on my friends pc which has windows 7 and all the Nexus 5 drivers installed. I myself have a windows 8.1 laptop and after one of the recent updates my phone stopped showing. I tried Wugfresh's Nexus root toolkit but I didn't get anywhere. Help? XP
There aren't really any advanced adb push or pull commands.
Regards to new problem see link in signature. Read section 1b.
On windows 8.1 I had to do 1b1 and 1b2 today
Sent from my Nexus 5 using Tapatalk
rootSU said:
There aren't really any advanced adb push or pull commands.
Regards to new problem see link in signature. Read section 1b.
On windows 8.1 I had to do 1b1 and 1b2 today
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled my previous drivers, updated windows and then reconnected my phone. Surprisingly the phone started showing! I had already done 1B1 earlier today. Thanks a lot guys. Everything has been solved. :good:
EDIT: I tried "adb pull sdcard/folder" and only the subfolders of that folder got copied, the files inside that folder didn't. Also, it said "no such directory exists" halfway through.
Awesome
Sent from my Nexus 5 using Tapatalk
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