Develop Bugs

[Q] Failed first rooting, help please!

I'm sorry if this has been asked before. I tried rooting my phone and this appeared:
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version '3.70.651.1'
Battery is at 100 percent.
The ADB Shell does not have root permissions.
Installing exploit...
Rooting...
Looking for Root...
Got Root!
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
hbootpreupdate set at '11'
Verified the phone has the older MTD setup with hBoot Version '2.10.0001'
Verified NAND is locked.
Setting RUU mode...
*
* Flashing Firmware...
*
* It is very important that you do not interrupt this while flashing.
* Unplugging or turning the phone off while it is flashing can easily brick
* your phone.
*
Rebooting...
Waiting for the phone...
error: protocol fault (no status)
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Giving the phone time to configure itself...
Rebooting into the recovery...
Waiting for the phone...
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
It failed and red exclamation mark screen appeared... I tried restarting and after the 3rd try, it worked. I was just wondering if I could try to root again and not brick the phone? I did it once and I'm a bit paranoic... Thank you in advance!

i would use unrevoked.
1. uninstall antivirus, where is my droid, or any app like that from your phone, make sure you have a full battery, if your phone screen is set to time out, change that to never or after 30 minutes(you change that in display settings), make sure you have usb debuging on(settings, apps,manage), uninstall or turn off your computer antivirus
2. download unrevoked
3. install usb/adb drivers from unrevoked site, go to more info on the site and download drivers, then extract to an easy to access folder
4. boot phone into bootloader and select usb at the bottom of the options, then plug to computer and your phone screen should read usb plug, it will try to install driver, select manually on your computer and look for the folder you just extracted.
5. install htc sync on computer and then uninstall it(you only install it for the drivers, but if you dont uninstall it you wont root)
6. right click on unrevoked file on your computer and run as administrator, follow instructions if any and your done.
hope it helps

Honestly had similar problem. Check to see if you have the HTC drivers installed properly. Also apps like PDA NET and other similar drivers can sometimes cause issues. My problem was my USB CORD. It was not connecting properly to my laptop (Toshiba). I went to Sprint store and got a new one. I ran the root program again and it worked fine. This might not be your problem however so, I only rooted a month and a half ago so maybe someone with more experience has more insight, but my USB cable was stock from 2 years ago and was kinda beaten up. Hope you find your answer tho
Sent from my PC36100 using Tapatalk

I just noticed that I get the red exclamation mark when I try to boot recovery. If I follow those steps, it won't mess up Recovery any further?
Sent from my PC36100 using XDA Premium App

Matafeka said:
I just noticed that I get the red exclamation mark when I try to boot recovery. If I follow those steps, it won't mess up Recovery any further?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
That just means that you don't have a recovery. You can't mess up a non-existent recovery, and even if you could, it's easy to flash a new one.
EDIT: Run unrevoked, it'll flash ClockworkMod Recovery for you and should fully root you. If you then want to flash Amon Ra, you can do so via Rom Manager or you can flash a PC36IMG of Amon Ra through the bootloader.
(from... Evo/MIUI/Tapatalk)

Thanks for all the help guys, got it working!!!

[TUT] ADB no device found -- Getting ADB to work

The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.

If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!

EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.

Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...

Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...

Is there a way for Linux?

D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.

Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.

DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.

that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.

tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.

Can you help/guide me on how to install it ?
Sorry for being a dummy.

Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...

RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.

rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...

Thanks
Thats Work

.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.

Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.

Can no longer connect via ADB

I had it all set up correctly and it worked fine both by USB and TCPIP. At some point in the last day or two this stopped working. I've done a complete reinstall of the SDK on my desktop and followed the instructions here https://devs.ouya.tv/developers/docs/setup
When I do adb devices I just get nothing. adb connect xx.xx.xx.xx gives nothing as well.
When I try to run adb from a terminal emulator on the unit I can start or stop the server but any other adb command results in a 'device not found' message. This message is preceded by some two or three digit word but since my TV crops the image I cannot tell what it says. so it is something like '##r: device not found'
Does anyone have any idea on what I need to do to get ADB working again?

Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2

TadeoNYC said:
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There aren't any drivers involved here yet. Nothing happens at all when I plug the system in. No devices are detected, correctly or otherwise.
I'm starting to think the micro usb port is just physically broken. I've tried multiple cables, restarting. Connecting other android devices to my desktop which work fine.

could be the port. I have a heck of a time plugging mine in sometimes. it's like the hole in the casing is just a bit bigger than the actual plug, and I have to fumble around for it. I mostly leave the microusb connected all the time now.

Oh!lol.
That happened to me as well. The micro usb port is deeper than normal. My Samsung plugs did not work,I was able to use one from my Kodak pocket video cam.
Sent from my SCH-I535 using Tapatalk 2

Ok, so I'm trying to just adb tcpip working now to bypass the usb issue. I installed an SSH server and I'm getting this
[email protected]:/ $ adb kill-server
[email protected]:/ $ adb tcpip 5555
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $

Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.

beowolfschaefer said:
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
Click to expand...
Click to collapse
If you have wireless adb enabled the way to control it so it does not shut down the micro usb port debugging , find the wireless adb .Apk here on xda in the nook color general section and install it then you will beable to open the app and toggle it back and forth to get micro usb debugging back.

My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?

Broomfundel said:
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Click to expand...
Click to collapse
Did you set up adb over wireless?

tcollum said:
Did you set up adb over wireless?
Click to expand...
Click to collapse
I had done but. But it stopped working some time after, and I have not managed to get it going since. Would it stop wired at the same time? Even so would it not have been reset by the factory reset?
Either way, Ill set it with an ethernet cable and see if the flaky wifi was why adb over wifi did not work.
I'm sure a workable solution will turn up. Just disappointed.
Ill report back.
Thanks
Update: Thanks for your help. I tried over wifi and no joy. But ethernet is working. So just got to sort out the flakey wifi now.
Thanks again.

Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta

For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!

HaYNigloo said:
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
Click to expand...
Click to collapse
It's also available through the f-droid app.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My wifi works great. unless i try to login to google.

Look here: https://devs.ouya.tv/developers/docs/setup
They changed the device ID, you need to do step 5-6.
More info here: http://www.ouya.tv/devnews.html

[Help] unbrick, Install rom from ADB

Hello guys, I need a lot of help from you guys
Today was changing the rom on my lg e977, but when I was formatting inadvertently deleted the sdcard also. I can access the fastboot and CWM with all the drivers installed, but when I access via adb I get the message
"* Daemon not running. Starting it now on port 5037 *
ADB server did not ACK
* failed to start daemon *
error: can not connect to daemon "
I believe I'm getting this message, because I believe that usb debugging was not enabled.
Anyone know what I can do?

now i'm getting the message:
error: device unauthorized. Please check the confirmation dialog on your device
but i cant boot the phone, so i need to enable usb debugging via adb, right?

Solved! Used this steps:
1 Make sure you have LG United Drivers already installed, otherwise download from below
2 Download Lg suport tool
3 Put your Optimus G into Download Mode by switching it off, attaching the usb cable to the phone, holding both the up and down volume buttons at the same time and lastly inserting the usb cable into the computer; wait for the drivers to finish loading if doing it for the first time.
4 when your phones conect to pc suport tool then go to software update
5 Click check in the first option. the program will close and a new one will open,wait for the flash process to finish.
6 you must have a internet conection, the whole process takes an hour or less. the phone will reboot when finish.
Sent from my LG-E975 using xda premium

Z1C power button is broken, need to turn on the phone

Hello,
My Z1C's power button have stpped working and currently my phone is off. I'm not sure if debuggin is enabled (and can't find proper guide how to turn it on using debugging)
Can anybody help me please!

my power button is also broken and here is how I boot the phone when it turns off
* debugging should be turned on and ADB drivers installed on the PC
while pressing the vol up button connect the usb cable to the phone (other end already connected to the PC)
the notification light should turn blue
start the ADB prompt on PC
run command adb reboot

karamancho said:
my power button is also broken and here is how I boot the phone when it turns off
* debugging should be turned on and ADB drivers installed on the PC
while pressing the vol up button connect the usb cable to the phone (other end already connected to the PC)
the notification light should turn blue
start the ADB prompt on PC
run command adb reboot
Click to expand...
Click to collapse
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
It get's blue light, I make a location adress to platform-tools, then adb reboot and get this message
I got this message. Can it be it doesn't recognise my phone?
i've used file transfer quite a lot, it should have autoinstalled drivers of my phone

TasKitas said:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
It get's blue light, I make a location adress to platform-tools, then adb reboot and get this message
I got this message. Can it be it doesn't recognise my phone?
i've used file transfer quite a lot, it should have autoinstalled drivers of my phone
Click to expand...
Click to collapse
Maybe it's because you didn't enable debuging in the dev options but thats another problem.
Try googling the error message, maybe you'll find a solution

karamancho said:
Maybe it's because you didn't enable debuging in the dev options but thats another problem.
Try googling the error message, maybe you'll find a solution
Click to expand...
Click to collapse
Probably it's off, thanks for suggestion

TasKitas said:
Probably it's off, thanks for suggestion
Click to expand...
Click to collapse
you should also try the fastboot reboot command