The right edge of my touchscreen has gone dead, not sure what the problem is, maybe the ribbon cable? I'm not sure, but I contacted htc and they said it's still under warranty and will be repaired (just so long as there's no physical/water damage, ect.) well my phones in pretty good shape, so I'm hoping I wont get charged.
However, I figured I should probably get back to stock and S-On
an quick tutorials on how?
This is why we have a Wiki, and a search function.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
If you have any particular questions, search first, if you can't fix them at that point, then post back to the thread for specific help with a problem.
I can't even figure out the first step :/
how do I check Gfree verify? I type that into terminal emulator, nothing heppens
Edit:
I'm not a n00b and the rest of the instructions look do-able, but how do I do gfree_verify?
bumpity bump bump
It's on the wiki page. You can find it if you search the page for 'gfree_verify'. I've linked the section for you below. Scroll down till you see '5. Verify the success of gfree'.
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
Thank you both very much
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
I go down to the next step, (and honestly, I don't know what my main version is) but when I use "# /data/local/tmp/misc_version -s 1.19.531.1" It says "permission denied"
Bump (sorry)
swee08315 said:
Sorry, I'm trying to unroot it, but it's not working.
When I "$ adb shell chmod 755 /data/local/tmp/gfree_verify" it says "no such file or directory exists
But i'm positive that I have gfree, so I decided to skip the verifying
Click to expand...
Click to collapse
You are positive the you have gfree.
Your device is positive you haven't got gfree_verify.
Guess who's right?
Follow Bharakrama's link, read, follow, success.
I too was sure I had adb and gfree but it wasn't working. I updated my android sdk and path variable and it worked again.
I'm also trying to return to stock. My gfree is working. How do I know if my main version is higher than 1.19.531.1? I'm using Cyanogen. Do you know how I find, or what the CID for Bell Mobility is?
I'm pretty sure I have Gfree, when I rooted it, it got unlocked and I'm now using it on at&t, that means I have gfree, doesn't it?
I'm thinking that I probably have footclans problem with the adb because I had ubuntu on thiis machine before and I just installed windows recently. I haven't had to use adb since then.
Try reinstalling ADB or updating the android sdk.
thanks, everything works now except this:
Disconnect the phone from USB and shutdown the phone.
Boot into hboot by holding <Vol-Down> while powering on.
hboot should load the PC10IMG.zip automatically and the ask you if you want to update. Press <Vol Up> to start the update.
After updating the radio hboot will start again (screen will get dark for some seconds)
If you had the fake S-OFF engineering hboot installed it will be replaced by this process
Click to expand...
Click to collapse
The text is too fast to read, but I think it says wrong image or something?
edit: theres a bunch of lines, and I think most of them say "no image"
bump bump.
my screen is really becoming very annoying to use now. I really have to get this factory reset soon so I can send it in.
I really need to get this figured out.
Sorry, but if I can get this resolved by the weekend, it would be wonderful.
anyone know why the factory image wouldn't be writing?
I'll try again tomorrow and record what is displayed across the screen if that will help.
Did you name the file right and check the md5 sum? Also make sure PC10IMG.zip is not is labeled exactly that! not.zip.zip unhide file extensions if your on windows. Also it must be on the root of the sd not in a folder of any kind.
Here's a screenshot of the zip on my sdcard
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and here's what happen when I boot with the volume down key pressed:
I also tried to use the following in adb shell, but I get permission denied
# /data/local/tmp/gfree -s on -c T-MOB010
Click to expand...
Click to collapse
Does that last screenshot help at all?
I'm busy with classes, and really need this done before the 1 year warranty is up.
Sent from my HTC Desire Z using XDA App
Related
So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...
PC-48 said:
So I have a rooted Evo and am wondering how the heck do I open up a shell? I'm trying to see if I my Evo is properly rooted and it says I need to open up a shell so I can check for this. I'm guessing it's like opening a Linux terminal but I have no idea how to do this on my phone and it seems like it's a fairly common thing. Should I have access to an adb shell after rooting? I am new to all of this so please go easy on me...
Click to expand...
Click to collapse
Just try downloading an app that requires root... like Titanium backup or wifi tether... all on the market...
or goto your tools folder from the SDK..with your phone plugged into your computer...on charge mode.... from a command prompt type "adb shell" and then if you get a "#" you are rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
that is for the terminal emulator for your phone. Or just grab it from the market:
'Android Terminal Emulator' by Jack Palevich
Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.
PC-48 said:
Ok so I downloaded that app using the barcode scanner and it runs so I must be properly rooted. I'm just wondering what the SDK is that apristel mentioned. I'm guessing Software Development Kit but I don't have one of those that I am aware of. I used the Terminal Emulator and typed in adb shell and it responded with "adb: permission denied". I'm just trying to learn about how all of this stuff works, Thank you for your help so far.
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
After you install that you will be able to open command prompt (windows) and type adb shell (when device is pluged in and in usb mode) to get shell access via your pc.
Ahh! Ok it's all starting to make sense now. By "usb mode" do you mean the Disk drive option or is it the Charge only option? I'm talking about the Connect to PC options...
I think he means usb debugging mode and charge only.
vbyt said:
I think he means usb debugging mode and charge only.
Click to expand...
Click to collapse
Yeah thats exactly what i meant. thanks for clearing that up.
I recently exchanged my g2 because the camera lens broke. I received the new g2 today it has gingerbread on it. I did not see any new root methods so do I need to downgrade to froyo or is there a new root methods or do the old ones work?
Sent from my HTC Vision using XDA Premium App
thugjedi said:
I recently exchanged my g2 because the camera lens broke. I received the new g2 today is gingerbread on it. I did not see any new root methods so do I need to downgrade to froyo or is there a new root methods or do the old ones work?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
First of all, that's great news for those waiting for an ota. Mind posting an about phone pic?
I don't think it is worth the hassle to downgrade, as someone will have a root method within hours of it's release. Though the leak was rooted... anyone else want to weigh in?
Sent from my T-mobile G2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hope this helps I just tried the original rom and it wont downgrade so just trying to root.
Sent from my HTC Vision using XDA Premium App
I thought we already got the ota is mine any different from the leak I can tell you its really fast and boots in seconds but there's no screen off animation
Sent from my HTC Vision using XDA Premium App
BUMP. I Second the OP's request. I did the signed non rooted manual push and wish I had rooted since there is now a rooted version of 2.3.3 floating around.
It seems to be the same as the leak, I just checked your numbers against mine. Mine doesn't have power on anime either. sad face.
so theres no way to root this right now
nope, none that I know of yet. Wait a few hours and check back. lol.
even if they find a way it will probably require HEX editing and i hate hex editing. I'll just wait for someone to root GB.
have you tried ginger break?
others have with no luck
EDIT: I just tried GB 1.2 and 1.1 both with no luck. i let them run for 10 minutes several times each and they just sat there with a spinning loading ring. oh well.
I have S-ON anyways, don't i have to have S-OFF before i can really root? IDK. I rooted my mytouch 3g a while back and have since forgotten everything.
When I try to install the signed 2.2 for the g2 to get back to froyo i get "main version is older - update fail"
skinnyveganboy said:
When I try to install the signed 2.2 for the g2 to get back to froyo i get "main version is older - update fail"
Click to expand...
Click to collapse
same issue
Is there another thread on this topic already somewhere else? I thought this would have blown up with comments by now...
There is apparently no developers working on this
Sent from my HTC Vision using XDA Premium App
I guess not. PLEASE, SOME DEVS START WORK ON THIS. thanks.
Have you been to #G2ROOT IRC channel and asked if anyone is working on it?
Sent from my HTC Vision using XDA Premium App
yea they suggested the gold card method and walked me through, it didnt work
Glad someone has tried the gold card method and saved us all the time. Thanks.
help
i followed all the step everything works out great until i try and downgrade. Once i type in the last command to change the version number it comes back with "permission denied". Anyone know why that is?
theunlockr"dot"com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/
They say that this way works.. but i get lost fast so if this works can someone write down the steps in a easy way to follow from start to end thank you
BEFORE YOU DO THIS, THIS WILL GET THE FIRST RELEASE ROM OF THE T-MOBILE G2
This version of the ROM you will cant use your phone as a hot spot and if it get over heated it will not power on
Download and unzip on your local hard drive
mediafire"DOT"com/file/24b44b44clc964b/AndroidSDK"DOT"zip
open a new cmd window
type the following
cd\
cd AndroidSDK\tools\
adb push fre3vo /data/local/tmp
(this will copy the file to your sd card)
adb push misc_version /data/local/tmp/
(this will copy the file to your sd card)
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
(this will run, once its done you will get a new line)
adb shell /data/local/tmp/misc_version -s 1.19.531.1
adb shell cd /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version -s 1.19.531.1
(this will run, once its done you will get a new line)
adb shell sync
adb shell dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
(this will run, once its done you will get a new line)
(leave this open cmd windown open)
open a new cmd window
type the following
cd\
cd AndroidSDK\tools\
adb reboot bootloader
(this will take you to your G2 boot loader menu)
fastboot oem rebootRUU
(this will take you to a black screen with HTC)
fastboot flash zip PC10IMG.zip
(YOU WILL GET A FAILED ERROR TYPE THE LAST COMMAND AGAIN)
And now you should have a black screen with HTC and a green bar in the bottom")
and your done you have the T-mobile G2 2.2 baseband 12.22.60.09bU_26.02.01.15_M2 kernel version 2.6.32.17-g814e0a1 [email protected] #1 build number 1.19.531.1 CL255798 release-keys
Hi,
I don't know how but my RSA key is missing from Winmax RSA key checker. no wonder I couldn't connect to my 4G network. I did make a backup using RA a while ago just to backup the Winmax key and nothing else. I located the folder on my SD and could view it from my RA recovery. But when I try to restore it...it says opps something went wrong and check your log file.
I don't know where is my log file and I don't know how to restore this key..any help would be greatly appreciate.
Thank you
place the wimax.img file on the root of your sdcard, open terminal, type
su
then type
flash_image wimax /sdcard/wimax.img
reboot, check for keys
Hi,
I did place the image file on my root under the sdcard and type "flash_image /sdcard/wimax.img"
but it says not found
i also created another folder called wimax and copy and paste my wimax.img in there as well and tried "flash_image /sdcard/wimax/wimax.img"
its also not found
i'm using terminal emulator if that helps
thank you
the file is named wimax.img? it is caps specific so if its named Wimax.img it will error
either change the name or type its exact name with caps etc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using Tapatalk
your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?
It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Clarification: the "not found" error you're getting is in reference to flash_image. Notice that you got the same "Not found" message when you typed "dir", since there is no dir command in that shell.
NewZJ said:
your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?
Click to expand...
Click to collapse
YES and still not found
jesuspgt said:
It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Click to expand...
Click to collapse
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks
hmm. used to have flash_image included. when did it change?
TommyNgo215 said:
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks
Click to expand...
Click to collapse
You really should follow the instructions on that link, they tell you exactly how you need to do this.
NewZJ said:
hmm. used to have flash_image included. when did it change?
Click to expand...
Click to collapse
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.
jesuspgt said:
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.
Click to expand...
Click to collapse
oh i don't have busybox i'm using Terminal Emulator. may that's why?
FIXED
download android terminal emulator, jack palevich author
it works in that one
Edit: not fixed
NewZJ said:
FIXED
download android terminal emulator, jack palevich author
it works in that one
Click to expand...
Click to collapse
Yea thats why i have...i downloaded that one Android Terminal Emulator by Jack Palevich but it doesn't work for me for some reason ((
TommyNgo215 said:
oh i don't have busybox i'm using Terminal Emulator. may that's why?
Click to expand...
Click to collapse
busybox isn't a terminal, it's the name given to the collection of command applications (for lack of a better term), that are used in a linux shell (terminal). Here's a wiki about it: http://en.wikipedia.org/wiki/BusyBox
If you don't want to use ADB, you can try just unzipping http://cyanogen-files.carneeki.net/flash_image.zip
It should just be flash_image in there. Stick flash_image into the root of the sdcard. after that, you should (hopefully) be able to begin using that command.
Edit: that zip file is not one that is flashed via recovery. It's just a plain old zip file. You just need to extract the file inside of it to the root of your sd card
its not that I don't want to use ADB but my knowledge is very limited. I got so confused from reading it and more confused from reading it again. SDK i don't have SDK i don't know what it is and then ADB i'm stupid. its crazy that i have an image here but i can't flash it using RA recovery.
ok i extracted..and still not found..it didn't install that to the phone. oh my what have i done
ADB is really not as complicated as it seems at first.
To get the SDK, go here: http://developer.android.com/sdk/index.html and install whichever flavor applies to you.
Assuming you're in Windows, just load up command prompt and navigate to the folder that the SDK installed to.
Plug your phone in, make sure that debugging is enabled in the USB settings on the phone, and then just follow the instructions step-by-step from that link. Those instructions focus at the end towards flashing a recovery image, but you will just need to substitute wimax in instead.
Hi Guys, Im attempting to gain root for the first time on my (Telus Desire HD). I am well aware that I need to downgrade but cant get, dont understand the following...
B.a Downgrade Process
1- Copy the PD98IMG.zip file from the "Step 1 - PD98IMG" folder and put it on the root of your SD card (i.e. not in any folders). Do NOT rename this file.
2- Go to the "Common files" folder and double click Start Here.
3- Copy the files in "Step 3 - Downgrade" to the "Common files" folder.
4- In the new command window that opens, type the following commands (you shouldn't get any errors. hit enter after each):
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell[/B]
When asked to copy the files in step 3- "Downgrade" to the common files folder... where was I supposed to locate this??? is it supposed to b on my computer C drive where it was downloaded to was I supposed to copy that too to the phone external drive.
Plain & simple the 4th step the new command window doesnt open & attempting to re-open after copying the files to the common folder doesnt give the "#" symbol when im finnished. Tried multiple times. Also phone is set to usb debugging... but should it be mounted, charge only, or htc sync?
Thanks any help greatly appreciated.
Not wanting to quite & keep trying I attempted to find out @ which step the cmd stopped working or responding. when entering the...
adb shell chmod 777 /data/local/tmp/psneuter portion of the above task this is the message that came back.
Failed to set prot mask (inappropriate ioctl for device)
I also noticed that htc sync stopped working after the first of 5 lines.
Also being a noob, I need to complete 10 replies before asking those in the development portion ss yeah sorry.
Another note: to which led me to the need to get root access soon is that telus just released an OTA update that doesnt work, so much that did work now doesnt or fails every 10 seconds.
Still no luck today, same responses as above.
All of the telus related posts I have read suggest using the same method but I havent read anyone getting stuck at this simple step so early on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get. I have also tried from other locations and I get the same result. Please help.
The attached is a pic of what i get in the cmd
the common folder is in the telus desire hd folder after you have extracted the package.
Thanks, I was aware of that. I think mabey the whole issue has something to do with the lame OTA update i just installed. It Changed my software # to 2.43.661.1
As I have been made aware by other topics... Version 2.3 + can not yet be downgraded.
Would be quite interested in knowing when I can downgrade version 2.43.661.1
Learn how to predict the future then Because nobody knows.
Sent from my Desire HD using Tapatalk
4.2.2 now enforces RSA authentication via ADB. This is only supported in later versions of ADB.
On Windows, you can see your local user profile folder's .android folder and see if there's a file called 'adbkey'.
Or use 'adb version' to see if you have the latest version. ADB version 1.0.31 is working.
Google just added this in the ADB protocol last November, so you need the NEWEST ADB:
https://github.com/android/platform_system_core/commit/d5fcafaf41f8ec90986c813f75ec78402096af2d
The keys for your hosts are stored at /data/misc/adb/adb_keys, I believe.
If your ADB works correctly, you will see this when you plug in for the first time. You may still have to reseat your cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Pic credit to rickbosch)
* * *
This will not affect all of you.
But on the stock Android 4.2.2 kernel from Google, I cannot get adb to work (always shows 'adb offline') on the stock kernel. This is with my laptop (a Lenovo Thinkpad), and I never had issues with this before with the same setup.
My current workaround is to use a custom kernel for 4.2.2 (thanks to renaud for delivering)
A custom Fugumod kernel that works with 4.2.2 and does not have this issue with ADB:
http://forum.xda-developers.com/showpost.php?p=37892325&postcount=2167
Stable builds (future?):
http://fugumod.org/galaxy_nexus/stable-4.2.2/
Please report back with the PC/Mac and possibly the cable you are using, thanks.
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
manumanfred said:
In default.prop is new line!
That is ro.adb.secure=1 or something like that, I think this is the issue! changing it to 0 may let you to use ADB!
I gonna test it out in 5 minutes.
Click to expand...
Click to collapse
That's default.
I resolved my issue swapping my kernel, not the ramdisk (that's where default.prop is in anyway). Hm...
rickbosch said:
It'll ask you to give ADB permission if you're all set up correctly. Mine did...Seems it's a whitelist system now where you can allow or not allow individual PCs to use ADB on your device.
Click to expand...
Click to collapse
This never came up for me . Didn't wipe though.
How do you manage devices?
I'm using 4.2.2 and I didn't got that popup!
I extracted boot.img and made it to insecure and changed adb secure line from 1 to 0 and now I can use ADB!
neither did I. Just flashed via TWRP over stock Takju 4.2.1
edit: And about managing devices, I have no idea.
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
xaueious said:
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Screenshot was taken on my phone, and about RSA key and ADB on Windows, I'm afraid I can't answer those for you.
xaueious said:
You shouldn't have to make ro.adb.secure=0 default. I think something is definitely wrong with this OTA lol.
Or maybe this is a new feature. Was the screenshot taken with Linux? How the heck do I get a RSA key with ADB on Windows?
Click to expand...
Click to collapse
Why not!
It lets to use ADB then, now I can use ADB without any issues, before editing default.prop I wasn't able to use ADB!
This is probably a new feature of some sort. Linux works fine, Windows doesn't. Mac probably works too.
Windows works fine for me. Maybe you changed something somewhere. I had 0 problems.
Never changed anything on the phone. Fixed the issue though. I was using an older version of ADB: 1.0.31
Older versions don't support key RSA authentication.
I also had this problem.
Then I deleted some spare copy of adb.exe and its dlls that where installed under \windows\ by some "do-it-all" tool and updated the adb tools with SDK-Manager.
After connecting to the PC, my GNexus asked for confirmation before allowing USB debugging and since then everything is fine :victory:
I updated android sdk tools on my mac today (before that I couldn't launch abd sideload update.zip) and haven't noticed any issues with adb/fastboot commands.
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
For me with stock kernel adb and fastboot ok.
I'm using bigxie rom deodex.
rickbosch said:
AH, so it's the outdated ADB drivers playing up, perhaps good to mention in OP as a solution.
Click to expand...
Click to collapse
Done
It may seem obvious for some, but wasn't for me.
I flashed the upgrade, with the cable always connected then couldn't get adb to work. Just need to re-plug the cable for the prompt to show up
Is this new version in the latest Android SDK? If not, where can you get it from?
EddyOS said:
Is this new version in the latest Android SDK? If not, where can you get it from?
Click to expand...
Click to collapse
Yes, it is in the new SDK.
On a side note, OP, the image you used and credited in the first post was mine, not manumanfred's.