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.

[Q] Xperia S Device not found for ADB sideload (WXP/W8)

Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?

itsMuppet said:
Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?
Click to expand...
Click to collapse
Did you try using the driver package that comes with flash tool?

v0ids0ul said:
Did you try using the driver package that comes with flash tool?
Click to expand...
Click to collapse
Yes, the driverpackage contains 3 sets of drivers for an Xperia S:
1. driver for ICS
2. regular driver
3. driver for GB
All drivers contains 2 inf. files: an ADB driver, which can be installed and a rndis driver which fails on Windows 8.
On Windows XP however, all drivers can be installed, but I still get an unknown device Xperia S, that surprises me a bit, because if it's unknown, how come it does know the name.

I had the same problem, and I found a site and solved it. But now, I can't find it! I just found this, Here:
forum.xda-developers.com/showthread.php?t=1583801
Sent from my LT26ii using Tapatalk 4 Beta

This might sound odd but have you tried uninstalling the "unknown device Xperia S" and then reinstalling the drivers?

itsMuppet said:
Okay, so the latest Cyanogenmod update went wrong and after a couple of tries I remembered power on and then volume up got me in recovery mode. I needed to flash anyway and wanted to try the android 4.2.2 and choose the OpenSEMC. When I installed it, I noticed that is was poluted with half apps from my previous state, so I made a backup of my SD storage and formatted the whole thing with TeamWin recovery projects 2.4.4. I than found out that this ROM software doesn't support USB mounting as CWM does. I'm now trying to get my rom to my device using ADB sideload, but in W8 as well as Windows XP I can't get my Xperia S driver installed. I've installed PC companion and tried a couple of loose drivers I've found, but in device manager I have an "unknown device" Xperia S, but no way to install the driver. The consequence is that in a command prompt using the command "adb sideload OpenSEMC-OTA-RC0.zip" the results are:
* daemon not running. startng it now on port 5037 *
* daemon started successfullt *
error: device not found.
Stupid me, realised later on that my backup's gone now as well. The drivers I've found all had a name according to the android version, but my problem is that there's absolutely no software on the thing.
Can someone please lend me a hand?
Click to expand...
Click to collapse
HI,
go to adbdriver.com and install the adb driver while the device is still connected.
Have a good day

i m facing the same problem whenever i connect my Xperia S with PC its Says Unknown Device USB not Recognised till now my Xperia S not connected to PC..

mkarande786 said:
i m facing the same problem whenever i connect my Xperia S with PC its Says Unknown Device USB not Recognised till now my Xperia S not connected to PC..
Click to expand...
Click to collapse
Uninstall the pre installed drivers from the device manager. Then try installing drivers again from flashtool.

Mirhawk said:
Uninstall the pre installed drivers from the device manager. Then try installing drivers again from flashtool.
Click to expand...
Click to collapse
plz read my threat -->> http://forum.xda-developers.com/xperia-s/help/help-help-xperia-s-t2867998

adb problems

Hi all,
today i tried to connect to my HTC 10 using adb and it wouldn't even find the device.
I updated the android sdk, which did not solve the problem. But i did find some other "fancy" things
First of all some info on my device
software: 1.95.401.4 stock
unbranded eu device
s-off and bootloader locked
phh's systemless root
systemless xposed
After i did s-off my device, i was able to fastboot flash twrp, adb was working, also after installing magisk and systemless root/xposed adb was working fine. When adb did not work i was like "perhaps i disabled usb-debugging, so enable it" but it was still enabled.
Here we come to another problem, with usb-debugging enabled, my mac/phone won't recognize it's plugged in via usb, a message pops up stating
Slow charge
For faster results, use the original HTC charger
Click to expand...
Click to collapse
if i then
uncheck usb-debugging -> the device gets recognized/recognizes it's attached to a usb port
a message pops up asking if i want to enable file transfer
rechecking usb-debugging -> device still recognizes it's attached to a usb port
a message pops up asking if i want to allow usb-debugging
running
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and
Code:
adb devices
List of devices attached
or
Code:
adb usb
error: no devices/emulators found
then i thought, ok revoke usb debugging authorization, unplug the device and plug in again, grant authorization and off we go, but i do not get the message if i want to authorize the pc
anyone else encountered this before or has any idea whats wrong here?
EDIT: it's working now, i do not know exactly why.
went into magisk manager to disable superuser and xposed to be able to rule out they were interfering in some way
saw magisk update is available so i updated magisk to v9
restarted without disabling modules
and now it works again. phone recognizes it's attached to usb even if usb-debugging is enabled.
EDIT2: can be closed by a mod as it's solved

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