Please forgive my ignorance I am very new to this. I just want to flash the new firmware to the nexus 9 manually. I have downloaded minimal adb and fastboot but it doesn't find my device. I have enabled developer mode and allow usb oem ect but nothing when I type the commands it says waiting for device and nothing happens, obviously I am missing something obvious, but if you could please help me out I would be grateful.
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
Not sure what the first question means??, I think I ran the adb commands at the right directory??
anobium said:
Not sure what the first question means??, I think I ran the adb commands at the right directory??
Click to expand...
Click to collapse
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
AjunNg said:
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
Click to expand...
Click to collapse
No never had a popup, asking me toconfirm???.
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
AjunNg said:
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
Click to expand...
Click to collapse
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Use Wugfresh's Nexus toolkit, and use the full driver installation.
anobium said:
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Click to expand...
Click to collapse
Right click on it. Go to where it lets you pick from a list on your computer. Choose android adb interface driver, or something along those lines
Sent from my Nexus 9 using XDA Free mobile app
AjunNg said:
Use Wugfresh's Nexus toolkit, and use the full driver installation.
Click to expand...
Click to collapse
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
No root needed to update.
anobium said:
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
Click to expand...
Click to collapse
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Migamix said:
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i get to flashing the image and it goes to quick and comes up with errors saying I have different firmware image on my device?, I thought that was the idea im going from lrx21r to lrx22c, do I have to put I already have the 22c in the option list??.
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
there is nothing wrong with ADB, or fastboot, if you use it exclusively, good for you.
as the OP title sais, it is not expected for a new user, and even some experienced users, to have such a firm grasp of the ways of the mighty command line, and the fact that the toolkit gathers all of the files in one convenient place, is not without its bonus. i dont know, nor do i really care who started the whole elitist "toolboxes are for lamers", or whatever. toolboxes are nothing more than their name suggests , tool-boxes, to help when we need it. they are nothing more than an interface to commands, much like you running a GUI on top of your OS, or are also running command line only for your primary computer. xda, is designed and expected to be help for all who want to know, not a pond of elitists that would rather brag they have overclocked their device, water cooled it, but can still make a grilled cheese sandwich on their CPU. i have email accounts older than many of the forum members here, so not too much impresses me in that 1337 area. im here to help if i can, and learn if i need to., so since im here alot, im always learning.
Related
-please read the whole thread-
:The point of this thread.
Find a way to get flash mode to stay active longer, Gives you more time to work and experiment"
The point of basing it on on the newer driver is that there may be something in them that will give us access to Fastboot"
Hopefully use that to get to the boot loader.
:--
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be useful.
It ejects when flash mode isn't used i think.
Sent from my X10i
jockep said:
It ejects when flash mode isn't used i think.
Sent from my X10i
Click to expand...
Click to collapse
No.
please just listen to me.
If any developer is interested in this PM me and i will explain.
Just a note but you may want to mention which version of the flash tool you are having issues with.
exsulis said:
Just a note but you may want to mention which version of the flash tool you are having issues with.
Click to expand...
Click to collapse
Please.. as i said DEVELOPERS ONLY.
PLEASE DON'T spam.
I'm not talking about the flash tool.
i don't think it has anything to do with the driver, as much as the phone's flashmode behavior itself.
ie the computer recognises the device device differently whether its in regular usb mode, debugging, mounted, flashmode, etc.
i think what it's experiencing is flashmode turns off if there's a delay, and changes usb mode. the computer sees the change as "device A" no longer there and "device B" now there. the computer will see the different usb modes as separate devices since there will be separate ID's for the mode.
if there was a way to keep the phone in flashmode, this would fix the problem. but there's no way of doing that without changing and reflashing fastboot/bootloader.
Then perhaps a driver that acts more like the drivers for the newer phones.
I think.. Fast boot could easily be accessed this way.
And all we need is for it to load that driver and to test using this command.
fastboot.exe -i 0x0fce getvar version
This is all speculation.. but call it a lucky hunch.
If i am wrong then the mods may delete this thread and XDA may ridicule me.
If anyone does manage to do this.
The credit is all yours.
No.. now i am sure the X10's driver may be buggy.
Hold the flash button and insert your charging lead using the wall charger.
You will notice it stays in flash mode for much longer.
I may be wrong.. but test it.
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
but don't get me wrong, if you or any devs know of a way to exploit it, by all means go to it!
svtfmook said:
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
Click to expand...
Click to collapse
I know this.. But i would like to get a few more developer opinions on this.
OmegaRED^ said:
I know this.. But i would like to get a few more developer opinions on this.
Click to expand...
Click to collapse
no doubt. would be cool if it could be exploited.
svtfmook said:
no doubt. would be cool if it could be exploited.
Click to expand...
Click to collapse
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
OmegaRED^ said:
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
Click to expand...
Click to collapse
Never head that on the x10 forums
Sent from my X10i using XDA App
rtblittlebrown said:
Never head that on the x10 forums
Sent from my X10i using XDA App
Click to expand...
Click to collapse
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
OmegaRED^ said:
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Click to expand...
Click to collapse
If other devs had that attitude they may already have picked this thread up
Seems you may have fallen foul of someones temper tantrum
Sorry for the spam
OmegaRED^ said:
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
Click to expand...
Click to collapse
If your plugged into your charger that happens on older rom's with charge when off problems
Sent from my X10 using XDA App
OmegaRED^ said:
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be usefull.
Click to expand...
Click to collapse
Not to throw a spanner in the works BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Edit: also some more research it indicates the its the android generic open driver inf
asmanthebell said:
Not to throw a spanner in the work BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Click to expand...
Click to collapse
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
This is why i asked for developers only to reply.
OmegaRED^ said:
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
Click to expand...
Click to collapse
Sigh!
1. Do you know and understand what an .inf file is?
2. Do you know how interacts with an operation system?
3. Can you post the rest of driver i.e the .cat file and .sys to go with the inf?
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
I have this exact same problem right now.
Would love to get a solution for this.
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
COLDrum said:
I have this exact same problem right now.
Would love to get a solution for this.
Click to expand...
Click to collapse
Please post here if you find a working solution for this.
demkantor said:
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Im on hold when it gets to downgrading so far. Im not familiar with Android Commander, but Droid Explorer requires adb to be working. And that is kinda my whole problem. I cant accept my PC as a secure adb-client since the digitizer is broken (touch input wont work). I hope there is a way to override this through recovery or some other way.
Breakdown:
When connecting device to computer (adb), I have to (on my device) accept my computer as secure. This is a problem since digitizer is broken.
Sent from my Nexus 7 using xda app-developers app
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
demkantor said:
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Indeed this seems to be a fix. Thanks!
Do you know if there is a way to get rid of the authorization through adb. Are there any files who could be manipulated? Would be great if I could use some sort of screencast-app eg. Droid Explorer.
Sent from my Nexus 7 using xda app-developers app
I'm sure being you can use adb shell in recovery that there is a way, can't say off hand but a bit of digging will probably get you there, it couldn't be all that hard I wouldn't think
Sent from my Nexus 4 using xda premium
Streaker said:
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
I do have more than one instance of ADB.exe installed yes, but does that matter to my problem? My Nexus isnt even showing up in fileexplorer in windows. So I cant access my files. Or am I wrong here?
Sent from my Nexus 7 using xda app-developers app
maxrfon said:
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
Click to expand...
Click to collapse
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
....
maxrfon said:
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
Click to expand...
Click to collapse
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have had the same problem with my S4.
After updating ADB i did "adb devices" and got my S4 as offline, and i noticed the popup on my phone, accepted and my samsung is now working fine with ADB.
FYI before the above mention operation i have tried everything, even making sure i run the correct adb.exe but there was no popup.
First of all kill the adb server via task manager then when you start the adb command-line type In ADB root this may solve your problem :thumbup:
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Somehow I managed to delete the stock OS and CM on my LG G2 (Verizon) and now my device is stuck on the loading LG screen. I am also getting the unauthorized device when checking ADB devices. I've got TWRP running as the bootloader, but just need to be able to push over the CM file to boot and I'll be good to go. Any suggestions on how to force the file over to the phone?
Boot into your twrp recovery and use adb sideload to flash a ROM from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
VreebieZ said:
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
Click to expand...
Click to collapse
I'm having the same problem as the OP... This is impossible. *the screen and digitizer are broken*
The question is "How can I bypass the New authorization, since I can't click anything on my phone". I can't check "USB Debugging" - I need the phone screen and digitizer to do that. come on people, read the post.
Has anyone figured this out? I'm having a similiar problem except my screen isn't broken. I forgot to make a backup and my OS got erased and I'm getting the unauthorized notification in ADB. You have to be able to get into the OS to accept the authorization so I'm at a catch 22. I have a Nexus 7 so I can't swap out a different SD card.
Hello XDA-Developers,
I've been a reader here for awhile now learning things about the android development for my devices and used many of your all members TUTs, but now i have came across a big issue that has broke my phone and need assistance getting it back online to be used with my carrier again. Below I'll explain my situation of what happen and what I need to be done so I can use the phone again or least get it back to factory stock so I can get a new phone... I will also offer someone $5-10 via PayPal for the assistance if you can help me get my phone back to the condition needed.
To start it off, I purchased a phone off a guy on craigslist, a AT&T HTC One M7 (Model: PN07120), when I purchased the device it was unlocked so I could use it on my carrier that was the reason I purchased it because I'm with T-Mobile. When I purchased the phone i went to setup the device to my needs and requirements and after two days of having the device, I noticed that the phone still had the previous owners information stored and was setup based on him, so because I didnt know the phone was rooted or anything, I googled how to factory reset my phone, so that way I could set it up to my wants, and requirements and below I'll explain the steps i'm at and what it is doing...
1. Searched google for the how-to method to factory reset my phone...
2. Went to 'Settings App', Backup & Restore, Reset Phone, Erase everything, Selected OK.
3. Followed the steps, phone rebooted..
4. Loaded up to the HTC (green logo) screen and stayed there...
5. Waited a few moments, phone never powered 100% back online just stayed at the HTC welcome logo when you first power phone back on.
6. So then I did the Boot Menu steps, (Hold Powerkey + Volume Down) to get into the boot menu,
7. When I got there it loaded to the boot manager window and I clicked FASTBOOT
8. Loaded new menu/logo "twrp" logo, then went to a menu "team win recovery project v2.6.3.3" with the list of options: INSTALL/WIPE/Backup/Restore/Mount/Settings/Advanced/Reboot.
9. I went to reboot to try to least get the phone booted, then when I was in the option to reboot, it gave me the warning of "No OS Installed", Continue without OS?"
10A. If I selected yes, it told me Install SuperSU, for root, otherwise phone wont be rooted.
10A1. I tried doing INSTALL SUPERSU did nothing..
10B. Did without installing SUPERSU and did nothing too, just when I boot comes back to this same menu Team Win Recovery Project.
So it seems I bricked my device as what everyone calls it to what I believe, I am unsure though or unsure how to fix this. I need to get the device either back to factory resetted to like the device comes out the box, so that I can use it, or what to do to get it back rooted successfully and working to be able to use the phone like i could at first.
I tried contacting the buyer but hes ignoring me now that I told him he told me the device wasnt rooted but the device was rooted and i seemed to have a major problem happen trying to restore the phone to factory defaults to set it up to my requirements...
My concerns and want is..
- My Carrier is T-Mobile USA LTE - So, I would have to get the device to stay UNLOCKED so I can still use the device on my carrier: T-Mobile, as it is a AT&T HTC One M7 Unlocked (Was working fine on my T-Mobile Sim prior to me trying to factory reset, besides the phone was named to the original owner and had all his settings and customizations that i didnt like or want.
- I NEED to get the phone back in a working condition. So please I'm really asking for your help I tried searching a couple articles here but couldnt find anything related to my situation.. This is why I am offering a payment for someone to be able to successfully restore my device back to working condition. Please help me!
- NOTE: When plugged up to the computer via USB Cord it did not connect or anything also. I also did not perform a backup because I didnt need any information that was currently on the device because it was the content and settings of the original owner i bought it from so I wanted to clear it all and set it up to my own.
- Overall, my phone is messed up because I tried factory resetting the device not knowing it was rooted, during the process found out it was rooted and now seem to have a bricked phone and need to know how i can fix it, and get android OS back installed, as it tells me there is NO OS installed when I reboot or try booting the device, and it remains at the HTC Bootlogo when powering it on without holding the power + volume down key to access a boot menu to perform a reset, install, etc, Like I mentioned I just want to restore my phone back to working condition even if that means to have to root the device again, etc. All I'm asking for is someone to either help me with each step or to write a step by step what I would need to do to recover and restore my phone.
Phone: HTC one m7 (AT&T)
Computer; Windows
Thank you,
PM or respond here.
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Where can I find this stuff I need to download? I tried doing a search and got a different version, Android Revolution HD 51.0, but could you please link me to the stuff I need to download on my computer, etc?
Okay I've done the steps you've instructed to me and I'm stuck at after launching the sideload feature on my phone; then going back to the computer and running 'adb devices' and under "List of Attached Devices" there isn't anything listed yet, and the phone says "Starting ADB sideload feature..." is the last line, I'm stuck with what to do...
I downloaded android SDK
downloaded the ROM
moved the ROM to the sdk folder where adb.exe and fastboot.exe are
launched adb sideload feature under advanced on mobile device
went back to the computer and ran, 'adb devices', and list of attached devices is none...
so I'm back at being stuck.
djay1127 said:
Hey again,
Okay I downloaded the android SDK, and I'm downloading the correct ROM now to install. Only questions I have for you is the following...
1) You said to move the ROM to where adb.exe is at... What do you mean by this? I don't have that file on my computer...
Where do I move it too once I have the android SDK downloaded and the rom downloaded...
Click to expand...
Click to collapse
Follow this video
http://android.mobilenicheapps.com/tag/android-sdk-installation
Sent from my HTC One using xda app-developers app
TopoX84 said:
Follow this video
[/url]
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I watched the video and got all of that working and checked based on the video and made sure all was installed, now i'm just still stuck at where you instructed me to do 'adb devices' after launching adb sideload under advanced on mobile, i did that, and i get
List of devices attached...
<nothing>
Then goes back to where I can type another command...
The phone itself screen is on the adb sideload feature, and in the textbox thing, shows the following
Updating partition details...
Starting ADB sideload feature...
then has a Cancel button underneath and then a loading bar underneath that... am I doing something wrong? or missing something?
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
djay1127 said:
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
Click to expand...
Click to collapse
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
TopoX84 said:
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried that and still get no devices attached.
djay1127 said:
I tried that and still get no devices attached.
Click to expand...
Click to collapse
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
djay1127 said:
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
Click to expand...
Click to collapse
Go to this website and download the HTC sync manager
http://www.htc.com/www/software/htc-sync-manager/
Once installed go to control panel > programs and uninstall a program... Look for the HTC sync manager and uninstall it, but leave the htc drivers alone.
Connect the HTC one to the computer and wait for the drivers to install automatically... After they are successfully installed try to run the CMD adb command adb devices
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Okay so I've done all that and after doing what you said, plugging the phone up to the computer everything installs besides the HTC MTP driver when the phone is plugged in. I still tried doing adb devices from cmd prompt to check and that didnt work still, no devices listed.
I get this error under the driver:
This device cannot start. (Code 10)
djay1127 said:
I get this error under the driver:
This device cannot start. (Code 10)
Click to expand...
Click to collapse
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
TopoX84 said:
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
djay1127 said:
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
Click to expand...
Click to collapse
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
TopoX;
You know this guy right here is clutch in my book.... He actually walked me through step by step, customizing how i needed it, fixing everything, and getting it back up and even though we had to do alot of modifications on my computer-end, him with TeamViewer literally fixed my phone, upgraded my laptop, and got my phone running better then normal and actually showed me how to do everything and taught me things I didn't know how to do with these Android Phones.
I am now very happy and thankful of XDA-Developers for allowing me to get this assistance and for having a great community with members like TopoX who literally saved my ass and restored my phone back to working condition and fixed my laptop all together, even though I was a brand new member with hardly any posts and not really much background, anyone else wouldn't of wasted their time... but he helped and even was up until 3AM ish doing it with me to make sure I got it back to exactly how I wanted...
We had to get the HTC MTP Driver installed correctly which kept failing/getting code error 10 (Unable to start) which if you google the issue it seems ALOT of people get this issue, and we resolved it by fastbooting and letting it install Android 1.0 itself, then manually updating my pc with windows updates and getting rid of the junk to stop corrupting and failing the drivers needed, then getting everything needed to flash my phone and re-root the device getting everything back in a working condition, unlocked, got that done and now phone is working better then before...
I'm currently running Team Win Recovery Project, ARHDOne-61.0 Google Play Edition, Rooted, SuperUser and Unlocked.
I personally wanna thank TopoX for everything he did and dedicating his time to helping resolve the issue for me.
TopoX84 said:
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
Click to expand...
Click to collapse
Cool story bro. Seriously..... Cool story.
I love XDA.
If anyone is trying too get in contact with "djay1127", please contact me on this user, my original first account djay1127 I can no longer access the account as I set it up with my Google account, gplus login, and I can no longer access that email, it's closed out. So I created a new account with my main email account and username.
I plan to contact a admin after doing some searching to discuss getting my old account removed, and the posts and crap merged into this account instead...
Regards.
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?