Related
1. DOWNLOAD USB DRIVERS
Motorola ADB Driver 32bit
Motorola ADB Driver 64bit
2. INSTALL THE SDK
-Download latest SDK http://developer.android.com/sdk/index.html
-Extract Archive to C:\SDK\ (or C:\Android, or whatever you want)
3. Enable debugging on your phone (thanks naplesbill)
-Goto Settings > Applications > Development > and Check the USB debugging option
4. Optional, but recommended
-Setup Enviroment Variables:
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path AFTER A SEMICOLON (;C:\SDK\tools\) .-Setup Droid Explorer:
Goto Droid Explorer Downloads and snatch the latest version, then install. (mine showed an error during install i believe due to the lack of HTC drivers. If you installed motorola's drivers it should still be in your start menu and work fine)
If for some reason you can't figure it out, install the drivers then try this installation guide: ADB For Dummies Guide
ADB APK Install instructions
j101399j said:
1. Create a folder called adb on your C drive
2. Extract all files to your adb folder
3. Copy the cmd.exe file (copy the file don't make a shortcut to it or move it) from your "C:\Windows\System32" folder to the adb folder
4. Install the downloaded USB driver
4. Once you have the driver installed, on your phone enable debugging mode (Menu --> Settings --> Applications --> Development --> Check USB Debugging)
5. Copy the apk files you want installed to your "C:\adb\tools" folder. The adb.exe and cmd.exe should be in that tools folder.
5. Open the cmd.exe file
6.Type the following command:
Code:
Code:
adb install [B]application.apk[/B]
Where application.apk is the name of the apk to install
Your app should now be installed
Please note that you cannot install apps used on 1.6, 2.x builds
Click to expand...
Click to collapse
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
Don't you still need root?
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
It doesn't help deleting the protected apps, but it makes it easier to install apks. This is especially helpful since the backflip doesn't allow anything to be installed through phones interface except through the market.
Ok, it works, but only if you turn on the Applications, Development, USB Debugging in the settings menus.
Well, that's kind of a given as ADB won't work without USB Debugging on.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
naplesbill said:
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
Click to expand...
Click to collapse
Ah, fair enough. Sorry about that.
Unimaginative said:
Well, that's kind of a given as ADB won't work without USB Debugging on.
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
Click to expand...
Click to collapse
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
@moosefist;
Thank you so much for posting this.
I am now able to install non-Market apps
moosefist said:
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
Click to expand...
Click to collapse
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Squeaky369 said:
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Click to expand...
Click to collapse
According to Skrilax_CZ a modmymoto moderator:
If we are up to root it; we need the shx/sbf flashfile, which must be leaked. Then I can see if the CLIQ RAMDLD exploit is present in here or whether has it been fixed as on the new CLIQ firmwares.
Click to expand...
Click to collapse
It was those files being leaked that allowed the CLIQ to be rooted...
I will be watching this thread closely I'm tired of having edge on my android....I need 3g for once!
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
JK_the_Slacker said:
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
Click to expand...
Click to collapse
This is from androidforums.com about this spicifically
http://androidforums.com/motorola-b...on-market-apps-via-adb-solved.html#post419647
On MacOS, ADB doesn't need a USB driver for your phone. Just download the SDK, and you can execute ADB from a terminal.
On Linux, all you need to do are to follow the instructions here:
Developing on a Device | Android Developers
Specifically the bit about creating and chmod'ing an /etc/udev/rules.d/51-android.rules file.
Hope AT&T fixes this issue soon, it's ridiculously stupid to attempt to disallow non-market apps given that ADB works.
Click to expand...
Click to collapse
j101399j said:
This is from androidforums.com about this spicifically
(URL deleted for forum reasons)
Click to expand...
Click to collapse
Thanks much, I'm just getting started on navigating all these forums. =)
Would it be possible for someone to create a utility to turn this option on, then load it via ADB? Or would this require root access?
BetterCut or AnyCut?
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
I don't have a Backflip, but it may be possible to find hidden settings / controls by using BetterCut or AnyCut. Both are in the Market.
I'd be interested in knowing. A crippled phone is a tiny electronic soul yearning to breathe free and live free.
I have a backflip, and just installed anycut. Do you know what I would need to fill in as the new shortcut to get to that option? I'm at work now, but will be doing the development method to install apks later under linux (gowalla app, most likely)
This is my first android phone, so I'm pretty excited to get it broken open and crapware free.
I just ordered the Backflip. Yes, I'm a newb at all this andriod, and rooting stuff. But, I'm in the process of learning more. I think it will be easier when I have the phone in hand to play with.
But, do you guys really think that someone will take the time to root the backflip, considering, (what I have read) that it is alittle out dated?
I'm going to attempt the non-market app install, once I get the phone. This forum is great, from what I've seen so far. I'll definatly be staying tuned to this thread.
Thanks guys,
J
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?
Hi,
Had a xperia Z3 (6603) for a few weeks now and looking at going down the root option already tbh. Just aggrivates me the limited access and the fact that apps are quite happily uploading/downloading data by themselves and could share personal info, etc. I keep my pc quite tight security wise and just can't imagine living with my phone being so open.
Spent several days trawling the internet reading up on it but tbh just came accross loads of spam sites offering `one-click` soloution programmes, etc and lots of conflicting information. Got myself more confused than ever with it all. Stumbled accross this forum which tbh seems to have one of the best reputations out there. I understand I'll lose low light camera functions but I can live with that tbh. Use my posh camera for important/work photos anyway.
I'm pretty computer savvy in that I can build websites and do a lot of CAD modelling/rendering, etc inmy spare time but some of the phone terminology is catching me out as all very new to me. Willing to learn though. Want my phone clean and clear so I can build it up as I want it and control everything moving on/off it with something like PDroid.
Can anyone point me in the direction of a `how to` thread/page? Need something step by step that I can't really go wrong with tbh. Any help greatly appreciated.
Right found this thread after a lot of searching. -
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
Off to do a lot of reading and researching my software number and unlocking bootloader, etc. Hope you guys don't mind some questions if I get stuck? Want to make sure I'm 100% certain on things before go ahead. Don't want to end up with a brick.
Ashamed to say I'm stuck already and it's not with the process of unlocking the bootloader I just can't seem to get the android SDK program I downloaded to pick up or detect the Java JDK I downloaded. Googled it to death and still can't seem to get it to pick up the JDK. 32bit system, windows 7.
SDK installed fine but wont start up and tells me to set up environment variable.
I've put the "JAVA_HOME" in my computer environment variables as described and put the link to "C:\Program Files\Java\jdk1.8.0_25". Still not picking it up though. Also tried a JAVA_HOME and a JDK_HOME with same link to folder and still no joy. It's definately the right path to the JDK. What am I doing wrong as driving me nuts!
As last ditch effort I logged off and logged in as admin and the program fired right up. Something to do with access rights I guess same as my dreamweaver software.
Now busy setting up n downloading updates, etc.
Good luck! I'll be rooting mine tomorrow evening I suspect... after it shows up at my door step
charlatan01 said:
Good luck! I'll be rooting mine tomorrow evening I suspect... after it shows up at my door step
Click to expand...
Click to collapse
Cheers. Steep learning curve for me as whole thing is new to me but chipping away at it bit by bit. Still downloading updates, etc but process itself seems straightforwards enough once got everything in place on computer.
Get bootloader unlocked then start looking at rooting process. Going to take me several evenings of effort n stress to do what someone knowledgable could do in 10 minutes but everyones got to start somewhere. :good:
To really help it sink in.
Write down all your steps from untouched firmware to root access and recovery.
It will help you to better understand the process and help others who are looking to do the same thing, plus it is a valuable tool if you run into any problems and need help
krankdroid said:
To really help it sink in.
Write down all your steps from untouched firmware to root access and recovery.
It will help you to better understand the process and help others who are looking to do the same thing, plus it is a valuable tool if you run into any problems and need help
Click to expand...
Click to collapse
Good advice, thanks for that. Printed out all the processes on paper and went over them all several times. Going to work through ticking off each item and taking photos of phone screen at each stage so got a log of everything entered, etc.
Biggest problem for me is the software tbh. The file sizes are huge and I have satellite broadband setup as live in remote area. Comparable to dial up download speeds. It took and entire day for the SDK programme to fully download.
Having problems connecting to Fastboot. Following the official sony unlock bootloader instructions.
Z3 connected to pc with cable, (holding down volume up button as connected), and blue light on. Next step on proceedure states "Open a command window on your computer and go to the `platform-tools` folder within the Android SDK folder before entering command "fastboot devices".
So what I'm doing is opening a opening a command prompt window through the windows start button and typing in the path to the `platform-tools` folder. Tried entering "C:\Users\John\AppData\Local\Android\Sdk\platform-tools" path in command prompt to get to the correct folder but just not accepting it. Am I missing something?
ianmoonescalpay said:
Having problems connecting to Fastboot. Following the official sony unlock bootloader instructions.
Z3 connected to pc with cable, (holding down volume up button as connected), and blue light on. Next step on proceedure states "Open a command window on your computer and go to the `platform-tools` folder within the Android SDK folder before entering command "fastboot devices".
So what I'm doing is opening a opening a command prompt window through the windows start button and typing in the path to the `platform-tools` folder. Tried entering "C:\Users\John\AppData\Local\Android\Sdk\platform-tools" path in command prompt to get to the correct folder but just not accepting it. Am I missing something?
Click to expand...
Click to collapse
try "cd" at the front of the command to change directories
Or just goto the correct folder and right click whilst holding shift and then choose open command window here
gregbradley said:
try "cd" at the front of the command to change directories
Or just goto the correct folder and right click whilst holding shift and then choose open command window here
Click to expand...
Click to collapse
Thanks got in to it now. `Fastboot` command itself works and lists options, etc but when enter `devices` or `fastboot devices` it doesn't recognise the command. Think I've buggered up somewhere. :/
My suggestion is not to bother with all that sdk,
Just install this
Minimal adb and fastboot
It has enough of the sdk to work with adb and fastboot
Install that, it should goto the directory of your program files
Navigate to it and open the command window there, then try it
You can also install flashtool from flashtool.net run the drivers.exe from the installation directory (In C:\flashtool\drivers) and choose flashmode, fastboot and Z3 drivers. That will ensure you have the correct drivers for the phone
EDIT
the correct command is
fastboot devices
You can also attach the phone turned on and try
adb devices
to see if you get a return, that way you know something is working.....
Tried the flashtool route using this guide - http://www.theandroidsoul.com/unlock-bootloader-sony-xperia-z3/
Installed the drivers, connected device and it brought up the choose device window. Clicked Z3 (66XX) and it says "bootloader unlock not allowed officially" even though on phone menu it says bootlocker allowed - yes
Looks like I cant do it. Hey ho.
Tried it again with the minimal adb and fastboot lin you mentioned. Installed the program and it worked fine and confirmed with an OK. Bizarre!
Phone now says Bootloader unlocked: YES
Onto rooting next. Thanks for the help. Greatly appreciated!:good:
Jeez, Sony provides a complete how to on rooting the phone along with the disclaimer on removed functionality. Look it up.
Sent from my D6603 using XDA Free mobile app
tweker said:
Jeez, Sony provides a complete how to on rooting the phone along with the disclaimer on removed functionality. Look it up.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
As far as understand. Sony provides a way of unlocking your bootloader, using a method where they require your IMEI number and then marks it as having a broken warranty in return for a unlocked bootloader.
That's not a service. That's damage control for companies trying to maximize their profit to not cover some smug bricking their device.
i would however love to learn more about this official grant of superuser access to the Z3.
Do you have a link ?
krankdroid said:
As far as understand. Sony provides a way of unlocking your bootloader, using a method where they require your IMEI number and then marks it as having a broken warranty in return for a unlocked bootloader.
That's not a service. That's damage control for companies trying to maximize their profit to not cover some smug bricking their device.
i would however love to learn more about this official grant of superuser access to the Z3.
Do you have a link ?
Click to expand...
Click to collapse
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Did I miss something, or is there another way to unlock the z3 bl without going down the Sony
route and surrendering your imei number to them?
No
3 day powercuts and big chunk of my roof missing thanks to 120+ mph storm. Joyous. Did manage to go through the root process though which went pretty effortlessly tbh.
Looking at sorting out my PDroid app and putting things back onto my phone, etc. :good:
The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?
schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?
GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.
GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery
I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.
.
H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?
Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?