Odin 3 running inside VirtualBox on PureOS, a Debian-based Linux distribution:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" and "Solutions to common problems" sections.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install" or something similar,
Install according to onscreen instructions,
NOTE: if you don't have an app like "Software Install", you can either install the downloaded file manually - How to install .deb, How to install a .rpm; or try to install VirtualBox with a package manager such as apt, synaptic, etc. However, VirtualBox may not be included with your distribution and it probably will not be the newest version. In either case, skip the above four steps.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
NOTE: If Microsoft gives you an error like: "We are unable to complete your request at this time. Some users, entities and locations are banned from using this service..." when you are using a VPN, then just start the download on a normal network, pause the download, switch to your VPN, and then continue - It worked for me!
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change the host-name to "Windows",
NOTE: You will need to remember your password, because even though you don't have to enter it every time, you will be required to change it every month, which requires your current password.
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to whatever meets your requirements (Just remember that Windows needs 20GB, Samsung firmware needs ~17 GB (You can store it on a USB drive though), and that the virtual drive does take up space on your computer),
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following (this unloads the "cdc_acm" module, which can be re-added by running "insmod cdc_acm"):
Bash:
sudo rmmod cdc_acm
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, click on the Windows logo in the bottom right, and then click on the power icon.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here. NOTE: If the VM is off, everything you plug in will open on the host OS, regardless of filters.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer from the Linux host onto the drive, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
Solutions to common problems:
If Odin is unable to see your device after following this tutorial try to unplug as many USB devices as you can from your computer (except your phone) and restart Odin.
If you encounter a "Kernel driver not installed" error when installing VirtualBox, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have any problems and/or questions, let me know.
Hope this helps!
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.
ethical_haquer said:
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.
Click to expand...
Click to collapse
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?
bmwdroid said:
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?
Click to expand...
Click to collapse
No, the virtual machine is stored on it's own virtual disk on the drive. I have shut down my computer many times, and the VM still runs fine.
bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
Let me know how it goes when you do it.
Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?
Pierro29 said:
Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?
Click to expand...
Click to collapse
You can use more than one CPU if you'd like, see here, but sometimes people have problems setting it up, and you don't really need more than one CPU if you're just using the VM for flashing. That's why I didn't include it in this tutorial. If you want more than one CPU to be used, feel free to though. Let me know if you encounter any issues when following the directions.
ethical_haquer said:
Let me know how it goes when you do it.
Click to expand...
Click to collapse
I will but didn't have the necessity yet.
Realized although that I may have to get another key from somewhere.
bmwdroid said:
Realized although that I may have to get another key from somewhere.
Click to expand...
Click to collapse
What key?
ethical_haquer said:
What key?
Click to expand...
Click to collapse
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
Activation is mandatory for this method ?
Another question, Odin V3.14.4 is better? or is it safer to stay with V3.13.1 ?
Thanks
Pierro29 said:
Activation is mandatory for this method ?
Click to expand...
Click to collapse
No, I think @bmwdroid is talking about something with his phone.
ethical_haquer said:
No, I think @bmwdroid is talking about something with his phone.
Click to expand...
Click to collapse
I meant the Windows key
bmwdroid said:
I meant the Windows key
Click to expand...
Click to collapse
What Windows key? I can head over to the Windows website I linked to and download it without any key.
bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
You can use a KMS activator. Free and easy
ethical_haquer said:
What Windows key? I can head over to the Windows website I linked to and download it without any key.
Click to expand...
Click to collapse
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>
bmwdroid said:
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>
Click to expand...
Click to collapse
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.
ethical_haquer said:
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.
Click to expand...
Click to collapse
You do not need a product key to use Windows 10. I think you can skip the product key prompt.
ethical_haquer said:
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" section.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install", or something similar,
Install according to onscreen instructions,
# Note: if you don't have an app like "Software Install", you can skip the above steps and try to install VirtualBox with a package manager such as apt, synaptic, ect. However, VirtualBox may not be included with your distribution and it probably will not be the newest version.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change hostname to "Windows",
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to 20GB,
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following:
Bash:
modprobe -r cdc_acm
cd /etc/modprobe.d/
ls
In the output from "ls" there should be one file, named something like "dkms.conf" or "blacklist.conf".
In the terminal, run the following, replacing "yourfilename.conf" with the output of the "ls" command:
Bash:
sudo nano yourfilename.conf
Add the following line to the file:
Code:
blacklist cdc_acm
To safe your changes to the file, hit Ctrl+x, y, and Enter,
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, type "shutdown /s" in the PowerShell.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer to the drive from the Linux host, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
If you have any problems and/or questions, let me know.
Hope this helps!
Click to expand...
Click to collapse
Hello fellow Linux user,
Might I suggest another similar method: QEMU and Libvirt (VirtManager). The only difference is it's lighter and more configurable than Virtualbox. USB passthrough is much simpler to setup in my experience and setup isn't terribly hard. I seem to have an issue with VBOX drivers, so this became my workaround for anything VM related.
You can install using the following commands:
DEBIAN:
sudo apt update && sudo apt install qemu virt-manager
ARCH:
sudo pacman -Syu qemu-full virt-manager
FEDORA:
sudo dnf update && sudo dnf install qemu qt-virt-manager
GENTOO:
sudo emerge --ask --verbose app-emulation/qemu virt-manager
Best regards,
D'Tor Aelek of Romulus
Related
I will no longer be updating this guide, to keep up to date with the project please see the App thread HERE. The Free app can be downloaded HERE and the Paid HERE
First and for most this guide has been created from a mixture of a few guides to get it all working on our phone, I do not take any credit for the methods all I have done is taken the time to work out how to get it working on our phone. This guide is for windows or can be done all on the phone. Anyway on with the guide
How To Install Ubuntu on the Desire S
Before we start you will need a ROM and kernel that supports loop devices.
This works best on lighter roms like cyanogenmod 7.1, however if you don't want to run a GUI it also works fine on sense ROMS. Please post any ROMS it doesn't work on.
It is also recommend that you have the Android SDK install so that you can access adb however all commands can be done on the phone via the terminal emulator
Also make sure that you have debugging mode enabled Go to Settings->Applications->Development and make sure USB Debugging is checked ON.
You will also need atleast 4GB of memory card space
Download and extract ubuntu.zip
Once you have a working ROM with loop support you must now download the special modified ubuntu image. I have hosted the file on my own server however if this is not quick enough feel free to mirror it or message me and I shall host else where as well.
There are now three versions to use as you wish, however the new 10.10 image has pretty much everything working, see change log at the bottom of the next post. the 11.10 image's UI does not work right and the 9.04 image is well rather old
[*]10.10 image V3 (Recommend)
[*]10.10 image V2 [*]10.10 image OLD
[*]11.10 image
[*]Old 9.04 image
Once you have downloaded this .zip file you will need to extract it to a folder on your sdcard name this folder "ubuntu".
Install and run Ubuntu!
If you do not have the android SDK install or wish to do all the commands via your phone please skip to step 7
1) Connect your Desire S to your computer via your USB cable and make sure USB mode is set to “Just Charge”.
2) Your Android device should be recognized as “ADB Device” under Device Manager. If not, install appropriate drivers.
For all HTC Android smartphones/tablets (such as G2 Phone, Nexus One), you can download Windows drivers here:
HTC Windows 64-bit driver download – Click Here to Download Driver
HTC Windows 32-bit driver download – Click Here to Download Driver
3) Now open a command window and navigate to the directory that you have installed the android SDK for example
Code:
cd c:\android-sdk
4) From here then navigate to the platform-tools directory
Code:
cd platform-tools
5) Now type “adb devices” to double-check your Android device is recognized. It should display something along the lines of
Code:
Lists of devices attached
HT09SR204261 device
If not then you have not installed the drivers for your phone or it is not in debugging mode.
6) Next type “adb shell” to enter the Android shell
7) Now type su to enter super user mode, then type cd /sdcard and then cd ubuntu to enter the directory on the SD card that you stored the ubuntu files.
Code:
su
cd /sdcard
cd ubuntu
8) Then type sh ubuntu.sh this will run the included script to ready your ubuntu image, do not worry about any error messages that are displayed!
Code:
sh ubuntu.sh
8.5) If running the 10.10 V2 image you should get this message 'please wait while booting the ubuntu img, please wait as this could take a while.' if you do get this then ubuntu is running and you just need to open vnc and connect to get into ubuntu. Please see the bug section on the third post for more information!
9) Now type bootubuntu to enter ubuntu (note in the future to start ubuntu simply type bootubuntu there is no need to run the script again)
Code:
bootubuntu
You should now see something along the lines of
Code:
[email protected]:/#
If you don't then its likely the ROM your using does not support loop devices and you will need to install one of the ROMs from the top of this guide to get it working.
And thats it you now have a working ubuntu command line running within android! however this isnt really much use so lets now get a more useful system running
How to Install TightVNCserver
This is by far the best program to install first off as it will let you access the GUI of Ubuntu as it run on your Desire S. (note this is already included in the 10.10 (V1 and V2) image there is no need to carry out this step)
0) Before you install any program first we need to update by typing
Code:
apt-get update
1) Now type “apt-get install tightvncserver” to install the VNC server.
it shall then as you if you wish to install the program etc etc say yes and it will install, simples.
How to Install LXDE (optional but recommended)
only need to carry out this step if you are using the 9.04 image
1) Type “apt-get install lxde” and ubuntu will do the rest
Set up TightVNCServer and fix keyboard issues
(note on the 10.10 image this step has been included already! so no need to carry it out)
Before we launch the TightVNCServer we much make changes the the xstartup file to change to it uses LXDE if we want this and also to fix a big issue with the android keyboard not being mapped correctly.
1) Start off by typing
Code:
cat > /root/.vnc/xstartup
To open the file we need to make changes in
2) Now type
Code:
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
export XKL_XMODMAP_DISABLE=1
icewm &
lxsession
The last two lines you will only want to type if you have installed LXDE if you want to use XFCE leave these lines off. The line above this (export XKL_XMODMAP_DISABLE=1) is what is needed to fix the keyboard mapping.
3) Now press ctrl+D twice and then press enter to the save the file, we are now ready to start up the VNCServer!
Start TightVNCServer
Now we are ready to start the server and connect our phone or windows computer to the Ubuntu running within our phone! (This step is not needed in the new 10.10 V2 image VNCserver now auto starts)
1) Start off by typing
Code:
export USER=root
vncserver -geometry 1024×800
you can change the resolution settings 1024×800 to the resolution of your liking. I find 800x480 does work well but limts your work space so its up to you.
2)TightVNCServer will then ask you for a password to connect to it, fill this in and your server will be then ready to accept any incoming connection from your phone or computer! (on the 10.10 image it will not ask for this, the password is set to ubuntu)
Connect to VNC on your phone
1) download the free app Android-VNC-viewer
2) open the app and set your IP address to 127.0.0.1 ( set this to localhost in 10.10 V2) and port number 5901 (5900 in 10.10 V2)and enter the password you set before (or ubuntu on 10.10 images) to then connect.
If all works right you will have a working GUI!!!
Connect to VNC on your computer
1)Start by downloading the desktop version of TightVNC Here
and install it
2) Open the TightVNC Viewer from the start menu it will ask for your phones IP address, to find this type ifconfig in your ubuntu terminal it will display your IP.
3)Type this into TightVNC and remember to add the port 5901 (5900 in 10.10 V2), it will then ask you for the password ('ubuntu' on 10.10 image) , enter this and you should then have a fully working GUI on your computer!
FAQ
How does Ubuntu look on our phone?
Ubuntu 9.04
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ubuntu 10.10
What is Ubuntu? and why would I want it on my phone
Ubuntu is a linux based operating system normally for the computer, however with this port we can run it on our phone, this allows you to pretty much install any software available for linux and run it on your phone.
What are the best settings for Android VNC Viewer?
I find full 24-bit colour works very well and there is no need to down step this, also Input Mode is best set to touchpad as the GUI is not very touch screen friendly when its this small! using touchpad makes the touch screen act just like the touch pad on a laptop and I find this very easy to use.
Updates
[15/12/11]
New 10.10 image
Included all updates as of today
Image resolution set by default to 800x480
[12/12/11]
New 10.10 image update
New built in script in Ubuntu to start vncserver and other services on boot
SD card is accessible from within Ubuntu
Image changed to 3.5GB to fit if you have a 4GB SD Card
The ubuntu boot scripts are now on easy to use script!
More working programs (including software centre etc)
Default desktop changed back to LXDE
More apps for 'developing'
Firefox, Thunderbird, openoffice.org suite, GIMP Image Editor, Emacs Text Editor (geared towards programming), C and C++ build-essential, Java JDK, Python, TeXlive and TeXmaker LaTeX editor, Transmission BitTorrent Client, eVince PDF Viewer, File Manager, Terminal, Image Viewer, Leafpad Text Editor, Synaptic Package Manager and Ubuntu Software Center with all repositories enabled (Ubuntu Software Center is pretty and well organized - but bloated and slow), SSH server, Gnash (GNU flash player/plugin for Firefox - as there is no official generla flash pluging for armel CPUs)
[23/11/11]
New 10.10 image
vncserver and bug fixes included in 10.10 image
New light weight UI in 10.10 image
4GB image size for plenty of app space
More programs should be working in the 10.10 image please test!!
New image all icons in GUI don't load Fixed in 10.10 image
New Firefox crashes on start up now fixed in 10.10 image
+More that I cant remember
[05/11/11]
Old 9.04 image readded for those that want working GUI until new image is fixed
[24/10/11]
Java install guide added
[23/10/11]
New 11.10 ubuntu 4GB image
Changed guide for new image
+MUCH more (will add later)
Bugs
At the moment to use the new 10.10 V2 image you have to carry out steps 7 to 8.5 each time in order to get into the GUI, which means the only way to use terminal for ubuntu is within the GUI, this isnt to bad as the build is now very stable
At the moment once you start ubuntu it seems to prevent the sdcard being mounted and as there is no way to shut down the ubuntu session you must reboot if you wish to mount the sdcard via usb
Java might still not be working right please test!!
Other Programs to Install
Ok so as I start working on testing more programs I will post here how well they work and what does and dosnt work. Most programs that run from terminal and don't require any hardware like wifi etc seem to work well!
JAVA SE FOR EMBEDDED
To install the Java version for arm open up the terminal and type the following lines of code
Code:
wget http://android.zpwebsites.com/java.tar.gz
This will download the java package from my server!
Once downloaded type
Code:
gunzip java.tar.gz
Code:
tar xvf java.tar
This will extract the java package into a folder called ejre1.6.0_27
then type
Code:
export JAVA_HOME=ejre1.6.0_27
Code:
export PATH=$JAVA_HOME/bin:$PATH
Java should then be completely installed, please test by typing
Code:
which java
Tips
Some android terminal emulators (e.g. better terminal) allow you to specify an initial command that is run as soon as you launch the application. Multiple initial commands can be defined by pressing return between each command when you define it, so for example the initial command:
Code:
su <return>
cd /sdcard/ubuntu <return>
sh ubuntu.sh <return>
This way to load the new 10.10 V2 image simply open the terminal emulator
Help Needed
I would love for people to test there fav linux programs, also anyone that knows alot about ubuntu/linux to help getting the image to run faster etc etc
:O OMG this is special xD
superkid said:
:O OMG this is special xD
Click to expand...
Click to collapse
im guessing your being sarcastic in which case, yes its the same as many guides across the internet however I could not find one for our phone, and the main purpose of this guide is for user to beable to find out what ROMs do work with it and hopefully create a better more user friendly ubuntu experience, after all when we can have around 300MB free ram why not use it for something like this?
I was not being sarcastic! its really special! UBUNTU ON A PHONE! i am downloading right now!
superkid said:
I was not being sarcastic! its really special! UBUNTU ON A PHONE! i am downloading right now!
Click to expand...
Click to collapse
AH alright then I hope that maybe more kernels will be produced that have loop support so this will work on more ROMS
main download link now up!!
you can download ubuntu.zip here
will def check this out
What is Ubuntu? Linux?
(Sorry for the noobie question)
shrome99 said:
What is Ubuntu? Linux?
(Sorry for the noobie question)
Click to expand...
Click to collapse
an operative system,it is free
anyway
finally,i m waiting this for a long time
Can i use the xda kitchen with this??
or anyway is it possible to cook rom on this ubuntu?
thanks
shrome99 said:
What is Ubuntu? Linux?
(Sorry for the noobie question)
Click to expand...
Click to collapse
It is a linux distro see http://www.ubuntu.com/
However please note for the time being the ubuntu we can use is 9.10 I will look to upgrade this soon mind you!
So, it's an OS for a Computer, like Windows?
shrome99 said:
So, it's an OS for a Computer, like Windows?
Click to expand...
Click to collapse
indeed its a compete OS that we can run within android on our phones! lots of programs are included and you can install more, but the likes of firefox works very well
Is it worth installing this instead of normal ROM ? I mean, what special can be done that can't be done with normal ROM ?
Is it possible to use this for everyday usage ? Is it possible to call with it ?
adridu59 said:
Is it worth installing this instead of normal ROM ? I mean, what special can be done that can't be done with normal ROM ?
Is it possible to use this for everyday usage ? Is it possible to call with it ?
Click to expand...
Click to collapse
At the moment you have to still install a normal ROM as this runs within android, the only requirements for the ROM is for it to have loop device support which the roms listed in the first post have that i know of.
People in the HTC HD2 forum where able to get ubuntu running without android being installed, it has also been done on the nexus s, my next steps will be to try and port this.
But for now this just runs within android calling etc is still done in android
Is my servers (the main link) download speed ok? or would your rather i uploaded it to multiupload?
I am a long-standing Linux user, so this is good! Do you have a screenshot of Ubuntu running? I am trying to work out how the GUI will scale on our phones.
Doesn't work using Zulugen 1.1.3 with CM7 kernel... :/
i m having issue with keyboard
do i need tightvnc every boot?
I've been looking around for some good tutorials, but in my opinion, almost everything was pretty difficult to understand for me.
But finally I found out how things are working (except of wifi, can You help me?
http://forum.xda-developers.com/showthread.php?t=1295718)
So I want to share my knowledge with You all and try to make it easy to understand.
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
2. Get the required files on Your Linux machine:
http://forum.xda-developers.com/showthread.php?t=1191141
On this link, in the second post is written flash kit for linux:
klick on "here" to download the flash kit.
3. Extract the flash kit into a folder (e.g. Desktop)
4. Now download the Ubuntu root files. They are located here:
http://rootzwiki.com/showthread.php?1072-ubuntu-on-the-transformer
You have to scroll a bit down then You see
"ubuntu-rootfs:
is available here md5sum(95eda389e64461533c51fd1e4e237a30)"
Again, click on "here" to download the rootfiles. (It'll take a while, since the file is 950mb)
4. Once this is done, extract the rootfiles into linux-flash-kit/images. (This folder is the one You have extracted in 3.
5. When You want to Dual-Boot Your device with Andoid AND Ubuntu, read on, otherwise go to point 6.
You have to download a nvflashable rom like for example "PRIME!"
http://forum.xda-developers.com/showthread.php?t=1251044
There You download the NVflash version and extract the image files in it, to linux-flash-kit/images, like You have done it with the ubuntu image file.
6. Now You have to choose.
If You want only linux: remember flash-purelinux.sh
If You want linux and Android Dual-Booting with Android as default OS:
flash-linux-android.sh
If You want linux and Android Dual-Booting with Linux as default OS:
flash-linux.sh
If You want to restore back to android: flash-android.sh
If You want to get to factory state: restore-default.sh
Now You have to install the APX drivers. How to do this, You can read in other threads. Basically download the NVflash file from this thread, in it, You'll find the drivers: http://forum.xda-developers.com/showthread.php?t=1123429
So connect Your tablet to Your PC, turn it off, and turn it on while holding down the Power Button and the Volume+ button.
What You'll see is nothing. Now Your device is in APX mode.
In Your Linux Computer, open up the console and go to the linux-flash-kit directory (In my case it is on the Desktop)
so I do:
cd Desktop\linux-flash-kit
So now You are in Your linux-flash-kit directory. From here You have to type:
sudo sh flash-linux-android.sh
OR You type this in what You have remembered in Point 6.
e.g.
sudo sh flash-purelinux.sh
or
sudo sh flash-linux.sh
This will take a while because the files are transfered to Your device.
7.
When it's done, Your device will start.
Turn it off, and start into Your Ubuntu.
When Ubuntu is Your main system, You start it up normally by pressing the power button.
When Android is Your main system and You are Dual-Booting it, hold down the power button and the Volume down key until the device says that Your have to press the Volume-up key. Do this and You will see a Linux code with two penguins on the top running down Your screen. That's just good like it is.
Finally You should see the Ubuntu Setup with the language selection.
Now You can go on, and now You can set up Your Ubuntu PC!
FYI:
When You have not got a keyboard-dock, Connect Your tablet with Your pc and enter the adb shell
When You don't know how to enter it:
open up Your console, get into the directory of the android-sdk and into the platform-tools.
Then You type:
adb shell
Now You should be in the ADB shell
Now You can type:
DISPLAY=:0 onboard
Then a virtual keyboard should appear on Your tablet and You're ready to go!
Just to create a vocal point, This requires root doesn't it?
Also, is the wifi and stuff working? What's not working?
Mr.Ox said:
1. The ony way in the moment to install Ubuntu on Your Transformer is over a Ubuntu or other Linux PC. (I easily installed Ubuntu virtually in VMware Workstation)
Click to expand...
Click to collapse
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.
roflcopterofl said:
Just to create a vocal point, This requires root doesn't it?
Click to expand...
Click to collapse
I don't think so, because everything is flashed via nvflash. This way, You can flash a rom without having it rooted, too.
But I'm not quite sure..
moseskim said:
Nice guide. There is one correction: it took me a while to find this but there is a windows-flash kit that I've used to install ubuntu on the transformer from Windows 7.
Click to expand...
Click to collapse
Oh, that's a nice one, I haven't seen this yet! Thank You!
asdfuogh said:
Also, is the wifi and stuff working? What's not working?
Click to expand...
Click to collapse
What's working and not You can read in the Q&A Thread, there is written everything, I just tried to explain it a littlebit easier.
The thread is here:
http://forum.xda-developers.com/showthread.php?t=1191141
There You can see what's working, what not, and how to connect to a WiFi network (For me it doesn't work...)
Thank for this, I am itching to try this... Is there any "easy" way to get back to stock honeycomb after i try this ?
(sorry for this stupid question, I do no know much about these things)
In my opinion it's very easy.
On the one hand, run the command
Flash-android.sh
Or
Restore-default.sh
Or your use nvflash to wipe the device and get a normal rom on it.
Sent from my HTC Desire using xda premium
Thanks, I will try this later today then
tombolek said:
Thanks, I will try this later today then
Click to expand...
Click to collapse
Yeah, when You get Your wifi working, please tell me how because mine does not work
Sent from my HTC Desire using xda premium
Hello yesterday i've try to put linux and android on transformer, all work's great but after 5 minut nvidia apx was disconnected because battery load 0%; i work on vmware machine; after I've charged my dock e tablet and run again the script but that's is the result
sudo sh '/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh'
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 2: /ubuntu/abootimg-i386: not found
/media/Nuovo volume/linux-flash-kit/flash-linux-android.sh: 3: /nvflash: not found
rm: impossibile rimuovere "linux.img": File o directory non esistente
why?
I've already tryed to restore with nvflash all partition and download all in new virtual hdd but not work.
Hello!!
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!
Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!
Doesn't work for me because I cant even see my S3 in the device manager.
leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"
help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher
familyguy59 said:
Hello!!
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!
Lucky Thirteen said:
...if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device.
Click to expand...
Click to collapse
Excellent tutorial... but I disagree with this line. No process is bulletproof and there is no way a tutorial can account for all the variables with Windows.
Which explains why I am now asking for help!
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed your tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
Please tell me you have a suggestion to help me fix this. I've tried using every combination of search terms I can think of and have had no luck for the past 36 hours.
Finally fixed my ADB problem using these steps in case anyone else runs into it.
This worked great for me after two days of trying to get my phone to connect. I had to uninstall everything related to java, android, and htc, and the link for the htc drivers was dead so I just reinstalled sync manager, but it all works now, much thanks. All this effort was just so I could put my music on the phone, and so that I could do a full backup to my pc without rooting.
Prerequisites:
Your PC must be at least Windows 7 Service Pack 1, although you must install every Visual C++ Redistributable Runtime and the Windows Device Recovery Tool.
Your Phone OS version must be at least 8.10.14219.341 or newer. If not, please update it using the windows insider app.
Have registered your device as a developer with the WP SDK.
Remove pin lock and turn off reset protection before the update procedure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossedlease follow this guide at your own risk as I am not responsible for bricked devices, dead SD cards or thermonuclear war:crying:.
Instructions:
1. Backup Your device.
2. Download Iutool (WP_CPTT_NT-x86-fre.msi) from the attachments section and install it. The default install directory will be
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
3. Download the M8.Rar that reflects your Carrier and extract the contents to C:\ on your PC.
M8ATT
M8Verizon
M8TMobile
Code:
C:\M8ATT
Code:
C:\M8Verizon
Code:
C:\M8TMobile
4. Open Command Prompt as administratior and change directory to where Iutool is installed.
Code:
cd C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
5. Plug your M8 into your PC and check to see if Iutool discovers your device by typing
Code:
iutool -l
If your device appears then you are ready to continue
If you met error 80070490 when executing iutool -l then disconnect your device and remove it from the Devices & Printers section of Control Panel
6. Assuming you extracted the correct zip into C:\ you are either going to type
Code:
iutool -V -p C:\M8ATT
Code:
iutool -V -p C:\M8Verizon
Code:
iutool -V -p C:\M8TMobile
That command will push the update to your device and it will prepare for the installation! Once the update is ready, take it! You'll want to find something to occupy your time as the process will take 40 minutes.
8. Once booted into W10 open Settings and navigate to the "For Developers" menu and enable Developer Mode.
9. Download and install Interop-Tools from it's respected thread and follow the For All other OEM Devices section to Interop/Cap Unlock your M8 if you had planned on doing so.
Interop-Tools https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
10. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
11. Now enable Windows insider preview builds and set to either slow or release ring.
12. Go into phone update and search for update. You should be brought to build 14393 or later. Updating to this build will fix critical issues/bugs you met earlier.
13. I also recommend a factory reset after all updates as that will reset Registry values to defaults and fix other things as well.
A HUGE thanks to @hikari_calyx for the Offline Update package V4.1 that he had put together over on the Windows 10 Mobile forums!
Another HUGE thanks to @gus33000 for Interop-Tools!
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
hikari_calyx said:
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
Click to expand...
Click to collapse
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
AnierinB said:
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
Click to expand...
Click to collapse
In some case, without modifying them, you can't search any update.
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
Click to expand...
Click to collapse
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
zagreo said:
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
Click to expand...
Click to collapse
ThIs is normal as I've encountered the same issue.
Bugs I know of:
Front facing camera sometimes causes reboot (switching from back in most cases)
Sound will sometimes only go through one speaker (works itself out but happens every now and then)
Flashlight toggle in quick settings has a long delay and sometimes doesn't work at all
Dot view doesn't work (but I personally delete the "extras" apps as the update process somehow made that possible for me)
Other than all that I'm pretty amazed at the way this devices handles the OS... every time I've gone back to 8.1 I'd instantly regret it after the setup
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Cokefrevr said:
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Click to expand...
Click to collapse
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
Click to expand...
Click to collapse
Everything work out?
AnierinB said:
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Click to expand...
Click to collapse
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Cokefrevr said:
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
AnierinB said:
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
Click to expand...
Click to collapse
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Cokefrevr said:
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
Click to expand...
Click to collapse
rayxanber said:
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Follow the for all other OEM Device section. Interop tools has changed a bit since I last used the device.
And yes that reminds me.. In worst case you can't get interop tools to work I'm afraid you'll have to change it before you do the offline update via The modified preview for developer's.. But no worries as the WDRT tool can bring you back to 8.1 NP.
Besides that.. How's the experience with w10 on the m8 for you guys?
AnierinB said:
[*]Your PC must be at least Windows 7 Service Pack 1, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool. Windows 8/8.1/10 are also acceptable.
Click to expand...
Click to collapse
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
AnierinB said:
(If you met error 80070490 when executing iutool -l, disconnect your phone, and delete your phone from Device & Printers section of control panel. Then reconnect your phone again)
Click to expand...
Click to collapse
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
AnierinB said:
Besides that.. How's the experience with w10 on the m8 for you guys?
Click to expand...
Click to collapse
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
AnierinB said:
11. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
Click to expand...
Click to collapse
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
reukiodo said:
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
Click to expand...
Click to collapse
Glad you got it working.. Haven't logged in to xda in a while because i'm using micro g on my Android device so sorry about the absence of help. How you liking it so far? HTC should have supported this huh? p.s lumia 735 works best for device spoofing.. 950 is unnecessary
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
nar001 said:
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
Click to expand...
Click to collapse
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
AnierinB said:
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
Click to expand...
Click to collapse
Am I supposed to do all this on my computer, or the phone? And I don't have the "NDTK" button on Interop 1.9 on my M8 (It's the AT&T version, if that helps)