Related
Well I try to root my phone i installed sdk and I did the adb but the cmd on my pc dose not see my phone all am trying to do is downgrade my phone so I can root how do I get the pc to see my phone it told me it hass adb but when I run cmd it dose not know its there plz help I really want this phone root it I been at this for the last 2 weeks
Sent from my T-Mobile G2 using xda premium
explain what you did and what you do exactly. Based on which instruction.
you're computer is a Windows VP / Vista / 7?
did you reboot afgter installing?
And post the command line you have.
We will without question need to know what you tried before anyone here can help.
Also, check to see if you phone was in USB debug mode. If it was not, no matter what you try it will not work.
I try to to downgrade my phone useing cm fourm on how to doundgrade a g2 well I use the coustom usb and I put it in the sdk folder were it was suppost to go well I try to run cmd and it tells me no such thing sorry not exacly what it says but close to what it dose tell me so now what do I do I really want a rom on this
Sent from my T-Mobile G2 using xda premium
First off, not to knock you, and I apologize if English isn't your first language, but you're posts are very hard to follow. Some punctuation and spelling would help immensely.
Second, you need to give us more detail. Step by step, as to what you are doing (commands entered, what error messages actually say, etc).
Third, some simple instructions are below, see if it helps:
1) Go to Start > Run (or hold the Windows Key and press R) to give you the run prompt.
See picture #1
2) At the command prompt, type in (without quotes) "cd\program files\android\android-sdk\platform-tools" NOTE: This is the path for default install for the google SDK installer with Windows 32bit. If you are running Windows 64bit I believe it is "cd\program files (x86)\android\android-sdk\platform-tools"
See picture #2
3) type in "adb" (again, minus quotes) to see the list of adb commands.
See picture #3
Hopefully you can take it from there.
Ok I have windows 7 well I download the sdk ok I was doing every thing from the cm forms well I all so did the thing with adb were on the cm forms it ask me to download the usb thing in place it in the folder were in extras sorry if miss spell I rann cumman prompt cmd it dose not see my phone that it it says here go this this in the forms look for need help that's my post to
Sent from my T-Mobile G2 using xda premium
Hey mate, I'd be willing to help you if you took your time (slowed down) and worked on your posts a bit. I tried really hard to understand what you're trying to tell us and I just can't get it.
Sent from my HTC Vision using XDA App
Can any one call me in help 614 962 1447
Sent from my T-Mobile G2 using xda premium
I tried to install sdk. Cm told me in their forums to install an adb in usb custom. The cmd does not recognize my phone.
Sent from my T-Mobile G2 using xda premium
Ok, so we will assume the SDK is installed properly. Then you open a command prompt and change the directory to the directory you installed the SDK using the "cd" command. From there you type "adb devices" and what is displayed on the command prompt?
We need to take this one step at a time. Everyone wants to help, but we need to be able to understand what is going on.
Can some one call me and help me plz 614 962 1447
Sent from my T-Mobile G2 using xda premium
Ok now the pc that my phone adb ok but when I put in adb divice cmd dose not see it and what's with this run thing all I do in my pc is run search for cmd
Sent from my T-Mobile G2 using xda premium
I think I understand what you are saying. So, you search for cmd in windows and then click on it to open. Once you do that you enter "adb devices" correct? Do you enter any other commands before "adb devices?" Also, have you gone to settings/apps/development and clicked Enable USB Debug on your phone?
I doubt you will find anyone willing to call you, but if you can clearly tell us what is going on; you will find help here.
Yes you are right I did adb devices but no other commainds but it tells me no external devices and some other stuff it says
Sent from my T-Mobile G2 using xda premium
And debuging good on my phone and sdk is on windows and under device manger it tells me my phone adb
Sent from my T-Mobile G2 using xda premium
This could be your problem. Before you enter "adb devices" you need to change the directory to where you installed the SDK. So, open a command prompt, enter "cd [directory where you installed the SDK]." Once the directory is changed enter "adb devices."
As for the location of the SDK, if you installed it to the hard drive it would be: C:\android-sdk\platform-tools. So you would enter "cd c:\android-sdk\platform-tools."
Try that and let us know what happens.
when I put this in cmd c:\program files (x86)\android\android-sdk\platform-tools it tells me file name derectory name or volume label syntax is incorrect
Sent from my T-Mobile G2 using xda premium
When I run cmd in put adb devices it tells me the system can not find the path specified
Sent from my T-Mobile G2 using xda premium
Can I plz get help
Sent from my T-Mobile G2 using xda premium
ok, these are not the recommended ways of gaining root, but your knowledge seems to be not good enough for the usual guides... (you are sure you want to root?)
here is one tool:
http://forum.xda-developers.com/showthread.php?t=1097977
or contact this guy:
http://forum.xda-developers.com/showthread.php?t=1500370
good luck (or ask for a remote session - i dont have time for this right now)
I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app
handman29 said:
I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go into device manager and install the ADB driver for the now unknown device.
I have the exact same problem, i used the driver that SDK manager downloaded.
In device manager its called "Android Composite ADB Interface"
but when i reboot Nexus 4 into recovery mode, windows does not recognize the device..
Update adb.exe to the latest version (from sdk) , connect and allow to use PC with ADB in android for the first time, then it should work in recovery also
Adam
I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app
handman29 said:
I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Install the naked drivers (found here on xda). And if sideload isn't recognized, your SDK is not up to date.
OK maybe my drivers..do you know if they work on windows 8
Sent from my Nexus 4 using xda app-developers app
Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app
handman29 said:
Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Did you select the adb option in recovery? If you did, then your drivers are not installed.
same problem here, i just downloaded SDK now, and the first thing i did was to use SDK manager to update the USB driver..
it does work when Nexus is booted in normal mode, but not in recovery.
i guess this is a windows 8 driver issue.
tried to install the driver from this thread:
http://forum.xda-developers.com/showthread.php?t=2019273
but it will not even install in windows 8
So there are different drivers for fast boot and recovery?
Sent from my Nexus 4 using xda app-developers app
I did a driver test from all in one tool kit and all the drivers work just not in adb recovery
Sent from my Nexus 4 using xda app-developers app
I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.
ravneetg said:
I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.
Click to expand...
Click to collapse
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.
same issue here; I tried to do it in linux (linux doesn't need any driver), using the latest adb (I downloaded the sdk this morning) but still nothing: Error device not found
I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
mashedbymachines said:
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery!
Click to expand...
Click to collapse
if you are still having issues, definitely try the naked drivers. I couldn't get other drivers including the SDK ones to detect my phone that is in recovery/sideload mode. The naked ones worked right off the bat.
whatsandroid said:
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.
Click to expand...
Click to collapse
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium
El Daddy said:
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted
whatsandroid said:
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted
Click to expand...
Click to collapse
Did you try the method which I posted? I was having the same exact problem.
ADB devices should work while in recovery.
Hi guys,
I'm currently experiencing a probem with my Nexus 4. No matter what OS I use (Linux or Windows) or what driver I use adb keep saying that my device is offline. As I saw elsewhere I tried an other usb cable or port but nothing seemed to work. Does anyone got an idea for this ? This thing is gonna drive me crazy !
Thanks
Task Manager, then kill the ADB one. Then open ADB, adb devices again.
Otherwise, did you check the debugging =.= Or reinstall the driver manually (not by WIndows).
I have had a problem with this and it has been unsolved as of yet, but I may be able to help you. In the SDK Manager, there is an extras area, if you don't have the drivers from there I have found you may have trouble. It could be something else, but this should be a sufficient launchpad.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Are you on 4.2.2 they changed somethings with the update. Have you updated your SDK?
Try installing PDAnet drivers. They will make it work.
xdaOSdev.team said:
Try installing PDAnet drivers. They will make it work.
Click to expand...
Click to collapse
I can verify this, it solved the problem I have been having for a few months in Linux OSes.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Guys, he said he's using ubuntu lol there are no usb drivers to install
try this...it sounds like your adb may be out of date. This will also reinstall fastboot, unless you leave 'android-tools-fastboot' off the last command
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
btw, if you haven't already done so, you should get the full sdk installed. It's better to have it and not need it than to not have it and realize after three hours of pulling your hair out you should have had it all along lol (I've done it, so I speak from experience)
Thanks @hp420 but sadly the device is still offline. I'm just realizing it now but I didn't have the warning message about the association with the computer that I usually have when activating USB debugging with 4.2.2
Load latest SDK version. Load driver inf fix. Search forum. Known problem. Easy fix.
sent from my nexus 4; cat on lap, beer in hand
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
No need for driver i'm running linux...
Sent from my Nexus 4 using xda app-developers app
Nark.GA60 said:
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
Click to expand...
Click to collapse
Tanks fort that answer I'll try it as soon as possible !
Sent from my Nexus 4 using xda app-developers app
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try a live cd of ubuntu and see what happens. that will at least narrow it down to whether it's your ubuntu installation or your phone. if it still won't mount in the live cd we can assume it's an issue with your phone. from there you can run a nandroid backup and reflash the factory images to see if that fixes the issue. if it does, you can try a fresh install of the rom you're using. if it still works, then restore all your apps/app data
if it's your ubuntu installation there are other avenues you can try.
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
scream4cheese said:
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
Click to expand...
Click to collapse
UBUNTU!!!!!
lol
hp420 said:
UBUNTU!!!!!
lol
Click to expand...
Click to collapse
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
scream4cheese said:
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
Click to expand...
Click to collapse
Thann you all for your answers! I use linux mint which is my main OS. I manage to resolve my problem in a weird way: first I push a CWM recovery with fastboot and then I flash the ZIP from SuperSu ! From now USB debugging is working properly and I get the usual warning !
What I would like to know now is why ? Does the SuperSU ZIP reset something ?
Sent from my Nexus 4 using xda app-developers app
I am generally good at rooting any android phone. I am having a hard time locating the drivers for the VZW LG G2. I have the zip file from the post on how to root the phone, but I am not sure which file to install.
Any input would be appreciated.
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
iowabowtech said:
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
Click to expand...
Click to collapse
I needed to install LG VZW_United_WHQL_v2.11.1 then go to LG website and download drivers from the G2 support page. I couldn't upload the exe file. Restart computer and all went well. I had same issue and struggled to solve.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Bxrider117 said:
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Click to expand...
Click to collapse
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
i'm having the same issue. i'm trying to root, and it won't list it at all, and i'm not getting the debugging icon on top. no serial number popping up on the abd devices and i just tried with both 3.8 and 3.10 drivers. anything?
If I remember correctly I had to go to settings>pc connection>select USB connection method and then choose Internet connection, then choose modem in order to get the debugging icon to appear.
Sent from my VS980 4G using xda app-developers app
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
thanks!
bigox said:
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Most likely it's because you don't have the right drivers installed. Try installing these http://g2-lg.com/download-lg-g2-android-usb-drivers-ver-3-10/.
Sent from my VS980 4G using xda app-developers app
The drivers aren't working for me so i will link where you can get the drivers from the actual website. Please note: this link is for Tmobile D801 but you can search for your device on there.
http://www.lg.com/us/support-mobile/lg-D801
LG's website has drivers for D800 and D801. I'm looking for D802 drivers. Where can I find them or which are compatible?
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
cggorman said:
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Where can I find Universal drivers? Not on LGs website.
I installed this:
http://forum.xda-developers.com/showthread.php?t=1379875
And after that it worked fine. I have a ls980, so the att and t-mobile don't work for me. This did.
This took me a while to sort out. There is a certain driver package for the verizon phone. The drivers listed here dont seem to work for me. I'm using win 7. Here is what I needed to use, then everything just came together - LG VZW_United_WHQL_v2.11.1
These can be downloaded at LG's site. Make sure you search for drivers pertaining to the model number of your phone.
Hope this helps someone
EVOme said:
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
Click to expand...
Click to collapse
I am having the same issue..what is the sdk with adb installed and what directory do i browse to? sorry for the noob questions, ive always had nexus's, so much easier to flash recoveries etc
LG Drivers failing to install
I Install LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe from LG website, it installs and I get a "successful" message from the software package. However, shortly after windows pops up a bubble with "not successful". Details:
Uninedntified Device - No Driver Found
Creative Game Port - Failed
Plug in phone and select “PC Software”, since none of the other options make any sense (USB charge, Media Transfer, Tethering, and Picture Transfer). Sidebar: None of the other options seem to change anything even when tried. "Media Transfer" is the only one that seems to actually install something successfully, but nothing changes with the device list. Back on track: Get a new windows “installing” bubble. Shortly after I get another “not successful” message with the following:
MTP USB Device – Failed
I go to Devices and Printers, select the phone, and look in the properties. Click “update driver” and pick the LG folder in Program Files. It says “driver already installed”.
Rebooting the computer accomplishes nothing.
I’ve tried several full uninstalls.
No matter what I try, if I run “adb devices”, I get “List of Devices Attached” then my prompt back, meaning none found I assume.
Yes I have turned on dev mode on the phone and I get the debugging icon when the USB cable is plugged in. I’m on Win7 64. WTF is wrong with this driver?
Thanks for any help you can give!
Uncheck usb debug? Had this on my htc one x. Maybe helps
Sent from my LG-D802 using XDA Premium 4 mobile app
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