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!!!
Related
Phone will not connect. I am using Linux Ubuntu and I cannot figure out why. I can detect on a windows computer but am new to Linux and am trying to install CWM.....
here is what is says
Original one clcik made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Phone is not connected. Press any key to continue.
I've searched and cannot find!!!!
When you get that message go ahead and unplug your phone from the usb cable and plug it in again. See if that helps.
Sent from my SPH-D700 using XDA App
thanks, but I have tried that multiple times... enough to the point of frustration where I would unplug, plug in, hit enter, (phone not connected)...Repeat x100 haha
Anything else???
Solved:
Figured it out.. just needed root access with the command:
sudo ./run.sh
took 2 times first time failed installation and then the second time it installed....
Im sure everyone posts about this but i used the one click auto root tool and everything ran fine up until the end when unrevoked forever or w.e its called was running. said it couldnt connect to daemon and now im stuck on white evo screen wont boot, keep trying to run the RUU but fails to run due to battery being under 30%. I was easily 75% charged before everything. Anyone else run into this problem? i just got my evo today and im feeling like i already failed at trying to root.
Note: i previously owned the htc hero, im a bit familiar with this rooting process, yet the evo is a bit tougher.
rooting issues
are you s-off or no?
Did you install the hboot drivers on your pc
Sent from my PC36100 using XDA Premium App
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?
devlon305 said:
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?
Click to expand...
Click to collapse
Does it say S-off or S-On?
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
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
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