Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.
Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all
Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem
Related
Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
thanks. I'll give that a try and reply back
Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work
phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?
chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.
Is USB debugging enabled?
CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!
No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!
I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!
You need to be in the tools directory of the sdk so cmd can find the adb command.
How do you gain temporary nand unlock? All i wanted to do is copy 2 files into the /system/xbin/bb which doesnt seem to work with root explorer despite super user permission, copy paste just wont work.
Any ideas how to copy paste these 2 files without going to full s-off? Would the adb method work? or any other apk that can do the job?
Thanks in advance for those who can help and any tips is very much appreciated.
In recovery with adb.
TheGhost1233 said:
In recovery with adb.
Click to expand...
Click to collapse
any links to it? a guide perhaps? thanks for the tip.
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
TheGhost1233 said:
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
Click to expand...
Click to collapse
btw, how do i get to adb with recovery?
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
TheGhost1233 said:
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
Click to expand...
Click to collapse
many thanks! i will try this tommorow.
Use the update.zip I attached in this thread, you don't need to worry about adb then.
http://forum.xda-developers.com/showthread.php?t=885506&page=2
Sent from my HTC Desire using XDA App
Ghettonine said:
many thanks! i will try this tommorow.
Click to expand...
Click to collapse
Ok I did my best, read alot about adb and followed some tips but I just cant seem to get these things working. I need a DETAILED step by step procedure.
I feel such a noob today, can anyone please help?
Basically, I just wanted to copy "ifconfig" and "route" from "/system/xbin" to "system/xbin/bb" and thats it! Im s-on by the way and dont want a full s-off just to copy paste 2 files.
I tried rebooting in recovery with adb and run some commands on "adb shell", many things came out and I have no idea what it ment.
Well many things came out is not such a great description. So i have no idea if something is wrong or something happened which you did not expect.
Boot again in to recovery and connect adb.
The type "adb devices" this should output something like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT##########
If this does not happen you don't have a connection and most likely have driver issues (only if you are on windows). If you do get a connection next thing to do is mount the system partition as read/write. To do this type "adb remount".
The output should be "remount succeeded"
Next type "adb shell"
This should give "#" as output .
Since you know where the files are and where you want them to go type "mv /system/xbin/ifconfig /system/xbin/bb" and hit enter, you don't get any conformation about this. Next type "mv /system/xbin/route /system/xbin/bb"
To check if they go moved correctly type " ls /system/xbin/bb", now you should see the files listed.
Next type "exit" to end the adb shell.
Then type "adb reboot".
If this doesn't work you need to give more info about the errors you get or maybe someone else has a better description.
A completly other method is, if you are able to copy the files to your computer, useing the .zip mercianary linked to, just make sure the system/app folder is empty and that you make the system/xbin/bb folder and place the files in there. Then just follow the instructions.
--This thread is recommended to be viewed on a Pc/Linux (I included you guys too ), OR on your ANDROID-POWERED phone (with XDA or in browser now ).--
--This is for PC and LINUX problems.--
Hallo!
You may have adb errors such as: cannot connect to daemon. This is a common problem beginners commonly forget. Also MAKE SURE you have installed android sdk
If you get adb error like :
adb server is out of date * killing***
daemon still not running
error:cannot connect to daemon
Click to expand...
Click to collapse
That means your device can't be found in adb.
Simply:
1) Make sure USB debugging is on
Found in Settings>Applications>Development
Click to expand...
Click to collapse
2) Make sure you have YOUR PHONES DRIVERS INSTALLED.
They can be installed via HTC Sync.
Click to expand...
Click to collapse
3) Still not working? Instead of using the USB option Charge Only/Disk Drive.
Use HTC Sync USB option.
Click to expand...
Click to collapse
________________________
RUU Problem [May encounter in the future](Thanks miguelca)
--Not for RUU Setup exe.
Out of date daemon error
Click to expand...
Click to collapse
Step 1) Browser to your android sdk folder
Its probably in: C:\android-sdk-windows OR C:\Program Files (x86)\Android\android-sdk (In 64bit edition of windows) OR C:\Program Files\Android\android-sdk
Click to expand...
Click to collapse
Step 2) Enter the platform-tools folder
Its simple just press Platform-tools
Click to expand...
Click to collapse
Step 3) Copy all of the files except: Source.propties, NOTICE.txt, lib, renderscript folder.
Hold Ctrl-A then press the files, then when done right click and press copy.
Click to expand...
Click to collapse
Step 4) Browse to your RUU Folder, and paste the files there.
Enter the RUU folder, right click anywhere press paste (If asks to overwrite press yes.)
Click to expand...
Click to collapse
Step 5) Should be done now!
________________________
[Linux ADB Problems (Thanks Tectas)]
Hallo, now this part of the thread is about linux ADB Problems .
permission denied ?????????
Click to expand...
Click to collapse
If you use Linux and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
[B][I][U][COLOR="DarkOrange"][FONT="Lucida Sans Unicode"]adb kill-server
(be sure the path to the adb directory is inside the .Bashrc file or CD to the right directory)
adb start-server[/FONT][/COLOR][/U][/I][/B]
Afterwards you can exit to normal shell and use it like ever.
[End of thread. Please scroll up or down to read reply's, or to read on ]
One addidonal thing,
if you are an linux user and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
adb kill-server
(be sure the path to the adb directory is inside the .bashrc file or cd to the right directory)
adb start-server
to start the adbd in su context, afterwards you can exit to normal shell and use it like ever.
It's not as trivial as you say. I had the out of date daemon error while trying to update my phone with the 2.3.5 European RUU by football. The solution was to uncompress the RUU and replace the ADB executable and dll's with updated ones from the Android SDK I had installed. It had nothing to do with USB connections or settings. Probably the RUU wasn't prepared for Windows 7 x64 SP1... I guess.
Sent from my HTC Wildfire S A510e using XDA App
Thanks!
Updated the thread.
XDA_h3n said:
Updated the thread.
Click to expand...
Click to collapse
You're welcome!
Thank you for the nice thread, for updating it quickly and for crediting me too.
It's great when several experiences are compiled in a way that might help many other users.
That's what a community is all about.
My trick is Download Vroot on your Pc and it will install everything you need. (Might replace your current Root Manager if you don't cancel the process of it rooting.) Once you connect your phone to your pc with Vroot it's ask you to install a apk just click okay. Once you see the apk installed wait for it to get a green backrground with wire connected image. Then there you go. Sorry for my Bad English. Hope it Helps.
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Raziel88 said:
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
In TWRP, go to advanced settings, click ADB Sideload, swipe to start sideload, and then type in adb sideload rom.zip
Raziel88 said:
can someone tell me a working adb ? i have to push rom.zip to phone's sdcard.. but couldn't do this job for hours... i downloaded some adb files, openned cmd, used "adb devices" command but it says device offline.. anybody here knows about adb things well and may help me please.. because my htc one m8 is just a souvenir on the table.. i wiped all phone and now can not open my sdcard on computer, everything fine device rooted TWRP is installed but need to push the Rom.zip to SDcard... i tried some adbs, but everytime it says device offline, so "adb push Rom.zip /sdcard command did not worked :S help me please...
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Did you change the command prompt to the directory where adb/fastboot is located at?
You can also try and download mini-sdk . Unzip it into c:\mini-sdk. Go to folder and hold shift and right inside folder then select open command prompt. See if you can then get adb devices to pick up device.
Raziel88 said:
openned cmd, used "adb devices" command but it says device offline.
Click to expand...
Click to collapse
You have a basic USB connectivity issue, so no adb commands are going to work.
Try uninstalling HTC Sync and any HTC drivers, then re-install HTC Sync.
If it still doesn't work uninstall them all again, then try to plug in the phone. When it tries to install HTC Sync automatically, cancel it. Go to Device Manager (if using Windows) find the device, select the option to install drivers manually and select Generic Android MTP device (or something to that effect).
Also, try a different USB port or cable; even another computer if possible.
ty friend it helped +1
Raziel88 said:
ty friend it helped +1
Click to expand...
Click to collapse
One of the solutions worked? Which one specifically?
redpoint73 said:
One of the solutions worked? Which one specifically?
Click to expand...
Click to collapse
finding the driver on device manager solved the problem thanks again :good:
Raziel88 said:
finding the driver on device manager solved the problem thanks again :good:
Click to expand...
Click to collapse
You're very welcome. Please feel free to click the "Thanks" button for any posts you found helpful.
USB connection was driving me crazy one time, trying everything else (various drivers, different ports, etc.) until I tried this simple solution.