Database Users

Ubuntu LiveCD with ADB and Unrevoked Recovery installer(Guide).

I have been helping out with rooting HTC Aria's over in IRC in the #liberatedAria channel for a while now. A lot of people have problems with drivers on Windows. The easiest solution for them to do this has been to download an Ubuntu LiveCD and use it to root their phone, however many people know nothing about Linux at all and feel daunted by this.
I have created a customized Ubuntu LiveCD that has a script that downloads the Unrevoked Teams reflash, untars it, and runs it as root to root HTC's phones that are supported by the tool (HTC Evo, Hero, Aria, Desire, and Incredible). It also has the Android SDK included and added to the path so it is accessible from a terminal. Everything can be done without a single change to the computer you are doing it on.
Download the iso image here:
MD5: 9a34c343e8f610e66674af9384334bf6
ubuntu-10.04-desktop-i386-HTCROOT.iso Primary
ubuntu-10.04-desktop-i386-HTCROOT.iso FileFactory.com
Burn the iso to a cd (This can be done with any cd burning software, imgburn found here is free)
[Optional]
If you do not have a CD drive, you can create a bootable flash drive by using the tool found here:Pendrive Linux
Put the CD into your computer cd/dvd drive and reboot your computer.
You must make your computer boot from CD, there are many different ways to do this depending on what computer you have, most recent computers have this enabled by default. Here is a guide that may help if you can't get this to work:Enable Boot from CD
Once it boots from the cd it will show a small picture of a keyboard and a person, do not press anything here and it will come to a window that will allow you to select your language.
Select your language and click "Try Ubuntu 10.04 LTS". This will boot up to a standard Ubuntu livecd desktop.
On your phone click menu, settings, applications, development, usb debugging
On the computer click "Places" on the top menubar and click "Home Folder". This will open a file explorer window, in that window is a script called "reflash.sh".
Double click reflash.sh. A window will pop up asking you what to do with this file, click "Run in Terminal". This will go get from the internet the current version of Unrevoked recovery installer from unrevoked.com/recovery, unzip/tar it, and run it as root.
Once it is complete you will be looking at the unrevoked3 screen and you should follow the prompts on screen.
You will then follow the prompts on the screen to plug in your phone, from the notification pane in android select charge only.
unrevoked3 will reboot your phone twice and leave you in ClockworkMod Recovery. On the computer at the bottom of the window it will say "Done".
Close the window, if you do not need to do anything further you can shut down the machine and be back in windows with nothing changed on your windows system.
Congratulations, your phone is now rooted and has ClockworkMod recovery installed.
There are other guides to setup of sideloading for the aria as well as how to load roms. You can do these using this live cd as well, this is a full ubuntu 10.04 livecd with only games and open office removed, and the unrevoked3 installer and the android sdk installed, it is already in the path and you can use adb commands from the terminal without having to switch directories(however it can be found in /opt/android-sdk-linux_86).
I would like to thank The Unrevoked team for making such a nice tool, and website that made this possible. I would like to that the guys in IRC on Freenode.net channels #liberatedAria and #koush for everything I've learned recently as well as all the great work they have done. Thanks also to Attn1 for making some nice roms for the HTC Aria and gave me the idea to create this. Thanks to Downer3d for the torrent mirror. Thanks to Neolobster for the new faster mirror.
Allowing Non-Market Apps using this cd on the stock ARIA rom:
Click Applications in the upper left corner.
Go to Accessories, click Terminal. This will put in you a terminal in the default users home folder. Because ADB(and android sdk) are in the path you do not need to change any directories. Start the phone in CLockworkmod with data mounted from the partitions menu and plug the phone into the computer.
Code:
sudo su
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
What this does:
Switch user to root.
ADB pulls the file that contains the setting to allow non market apps down to the machine from the phone.
The next line runs a sql update of the field install_non_market_apps in table 'secure' and sets the value to 1 (on).
ADB then pushes the file back to the phone in its original location.
You then use ADB to reboot the phone to enable it.

Thats awesome!! If I didnt already go through all the trouble of doing it on my Windows box I would definitely try your live CD. I already have 10.04 installed on my laptop and I never really thought of trying it on there. I wonder if it would have been easier....oh well. Thanks again. Im sure there are plenty of people out there that will find this very useful.

Much easier. And yes, this IS awesome. Great job, Shad0wf0x. This kicks ass.

This is a fantastic idea, I had a ton of trouble rooting my Aria on Win7 x64 and downloading and using Ubuntu 10.04 eventually proved to be much easier. If your iso works as advertised I can see this possibly being the most pain-free solution for annoyed Windows rooters.
Sent from my HTC Liberty using XDA App

This works wonderfully for rooting and sideloading apps (the only issue there was figuring out I needed the root account and permissions). As painless as a dentist trip.
If I was to install Ubuntu from that LiveCD, would it still have the Android SDK on it or would I need to reinstall it? I like not having to cd to it.

the android sdk is installed on the livecd and in the path, you'll have it every time you boot up, the part the script downloads will be gone on a second boot(unrevoked.com's recovery installer)

Great job!
Do u think that u could add some other HTC devices, in the future?

Awesome, thanks!

matteios said:
Great job!
Do u think that u could add some other HTC devices, in the future?
Click to expand...
Click to collapse
The devices supported are the devices supported by the unrevoked3 tool, I am not part of their team, just trying to help out some windows users who have driver problems.

Virtual image?
Has anyone created a virtual image of s full Android dev system? That would sure be handy!

jmdearras said:
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
Click to expand...
Click to collapse
not sure if this is what you're looking for, but it'll help.
http://forum.xda-developers.com/showthread.php?t=701816

Problem with reflash.sh tool
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003

jbwfg said:
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
Click to expand...
Click to collapse
it says in your signature you have 2.2 updated OTA, that must mean you have an evo, and those aren't supported by the unrevoked tool when running 2.2.

awesome shortcut for rooting phones, however I followed the steps and it is saying that the hero is not supported at this time? Did i do something wrong, I'm running 2.27.651.5

I've burned the the iso file to a cd but I'm not able to get the boot-up to work correctly..or to come up at all, when re-booting windows.

@lcw
When you boot, you will need to hit your bios and select your CD drive as a boot device. Then enjoy the ride - easy as falling off a bike.

I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.

pinkpanther2000 said:
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
Click to expand...
Click to collapse
You're not supposed to burn the ISO file onto a disc as a file. You're supposed to burn the contents of the ISO to a disc.
Sent from my HTC Liberty using XDA App

I attempted to boot from the CD, I get the person/keyboard screen then i get the Ubuntu screen, then my computer goes black, any solutions?

This is the BEST way to root your Aria. Big props to everyone that helped create it. You guys are the best.

Anyone know of an idiots guide?

I've just about given up. I downloaded all these programs, drivers, other stuff. I thought I had all the required software. I tried to run adb.exe and it just opens a command prompt and closes right away. I've tried searching and all the guides says download this....this..and this..once you have it all. And it starts from there.
The problem is i downloaded everything and I don't know if its working properly to start adb.
I hate this.
I've even thought about downloaded a whole other OS and running it from my USB drive to see if it's easier.
Anyone know of a good how to video?
I know that's what i'll be making as soon as I get this up and running.

Are you actually running adb through a command prompt or just double clicking the exe?
Sent from my T-Mobile G2 using XDA App

CMP
take a look.
http://www.youtube.com/watch?v=-rTOy5oN0GM

use cmd to run it

Start -> Run -> Type cmd -> Enter
cd whatever/directory/adb.exe/is/in
adb

you should just add the android tools directory to your PATH makes life much easier.
Sent from my T-Mobile G2 using XDA App

Yep editing the path got it to work for me.
Sent from my T-Mobile G2 using XDA App

They are aren't they? The vid shows them in there.
Sent from my T-Mobile G2 using XDA App

if you are having that much issue setting the correct path, just go to your system 32 and copy over the CMD.EXE to the folder you are working in with Android. And then launch CMD from there.
Or just type into command prompt
PATH = %PATH%;C:/Android/Folder/Youre/Working/With/
EDIT:
I just watched your video. You have some problems in there
First, you aren't setting a new path, you are (attempting) to change your working directory in that video, however you are not doing it right.
You have to use the 'cd' command
C:\Current\Work\Space > cd C:\Change\to\this\space
C:\Change\to\this\space > adb devices
bleh bleh bleh bleh
But it would be better to just do the above method.

In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.

"Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt."
Also, add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android\tools
If you happen to upgrade to Win7 you can easily open the CMD by shift right-click inside the window itself.....applying the path automatically for you.
You will also have too use these drivers located here: http://forum.xda-developers.com/showthread.php?t=802316
or
Use notepad++ to edit that file and add the following lines to the "google.ntxhe "" and the "google.ntamd64" sections:
Code:
;T-Mobile G2 %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91 %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01 ;
Save the file, reinstall drivers, and done...
Click to expand...
Click to collapse

smasraum said:
In most cases, the instructions are pretty clear. If you read the instructions on installing the SDK, it tells you how to set the path.
http://developer.android.com/sdk/installing.html
If you follow instructions, then you should be good to go.
If not, then you should be able to do something like a google query for "set path variable windows < whatever kind of windows you're running >"
If you're having a problem getting that stuff done, then maybe you should rethink rooting your phone. I don't know that anyone has bricked a G2 yet, but LOTS of folks bricked G1s. I think it's only a matter of time before someone figures out how to thoroughly break a G2.
Click to expand...
Click to collapse
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.

ddgarcia05 said:
Thanks, looks like I'll be waiting it out. I didn't think it took this much know how to get sdk and adb running properly. I was able to change the path but ran into another brick wall. I type in abd devices to see if it was recognized and nothing. Like i said, I'll be waiting it out until a more permanent route can be found, and more support for rooting is available. Besides I don't think anyone wants to hold my hand and walk me thought the whole thing. It gets annoying, believe me I know. I'll be doing a how to video once I learn to get it all working and when a permanent root is available. I'll learn on XP and make the video using my Win 7.
Click to expand...
Click to collapse
The G2 isn't included in the current adb drivers that you download separately/with the SDK. You have to edit the inf file to have the G2 recognized. There has been at least 1, maybe a few threads with the lines to add here. I think there's a thread titled something like "I can't get adb to work with my phone" or something like that.

looks like i was doing it right. I was typing "abd" instead of 'adb" it founy device.
Now I guess the have to start sending the files over....
I typed "adb devices" and it picked up my device. with my phone's id number.

I am also about to give up. Some of us are new to Android.. we don't understand SDK and ADB and all these other programs. I do plenty enough reading.. but for some reason can't get these programs to run on Windows 7 x64.
I mean is their a newbs guide for the G2.. for rooting and such?

Yeah there is but you have to read like three guides and watch two videos to fnd everything you need. Ill try to make a quick how to after I finish up mine. I just have to push the apps/install the apps. Did you find the java jdk version. And do the commands on your computers cmp?
Sent from my T-Mobile G2 using XDA App

I always used this guide:
[GUIDE] ADB, Fastboot, and Nandroid for Noobs
Hope it helps
Use the drivers in post 11 in this thread
Unless you rooted your G2.........adb shell will NOT work.
ADB shell needs root access

Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App

ddgarcia05 said:
Thanks, I have already rooted my phone. Unfortunately my wifi tethering doesn't work. It always says no network access so I'm just going to leave the phone as is until the update comes in.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
why not use VISIONary app to root the phone for you?

konoplya said:
why not use VISIONary app to root the phone for you?
Click to expand...
Click to collapse
At the time it wasn't available, but I'm using it now.

[Q] ADB not recognizing, please help

Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.

If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk

neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb

corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App

Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)

So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.

i really dont understand

I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.

mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!

Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.

You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G

ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.

tried your directions again
I have tried them again and they do not work.

Try the usb cable for the droid x. Its a really good one.

if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.

mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G

thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.

mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!

I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.

SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.

I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk

[GUIDE] Workaround for attaining S-OFF (for Windows 8.1. users)

For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)

Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?

painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.

EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.

sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:

skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.

Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app

alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app

I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)

Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1

I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app

roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app

Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app

My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk

punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app