Many Linux users have complained that heimdall is difficult to use and they don't have a Windows machine to use Odin. I just want to confirm that Odin in a VirtualBox Windows session DOES work. I just tested it on my T510 to install LOS 17.1. Just make sure you install the "extension package" and the "additions" and add your user name to the last line in the /etc/group file. You need to use "sudo" in a terminal to open the file with a text editor.
Related
Looking for some assistance getting the NDK working properly on Windows 7 (64).
I followed all of the instructions to set up the NDK in windows but am running into an issue.
Per the instructions you need to install CYGWIN which i did and then go to the root NDK folder and run build/host-setup.sh.
Once I run this i get the following error;
ERROR: Could not find a valid GNU make executable.
Please ensure GNU Make 3.81 or later is installed.
Click to expand...
Click to collapse
I do have GNU make 3.81 installed for windows.
If i try to use cygwin to run a make APP=hello-jni as a test as it states i get the error;
bash: make: command not found
Click to expand...
Click to collapse
if i use windows command prompt i can run the make.exe fine.
I'm thinking the issue is because its trying to use a Linux based make since i would assume Cygwin cannot rune EXE files.
Could anyone assist me with this that has it set up and working properly in windows?
Any takers please?
Check 'Make' package in Cygwin setup.
Do yourself a favor and use a real operating system. Ditch that MSJUNK.
On top of that, I *strongly* suggest that NOBODY EVER use windoze for compiling ANYTHING. When you are building software for other people to use, you most *definitely* do NOT want to build software that has been compromised. Windoze is the world's number ONE compromised platform. It about as save as having your way with a 50 year old street corner hooker without protection.
best program to open a .img file
bycoo222 said:
best program to open a .img file
Click to expand...
Click to collapse
Daemon tools -> create virtual drive > mount disk.img
Anyway...depends on which android .img you're trying to open. Personally i wouldn't bother doing any of that on winblows.. download a linux distro and dual boot (wubi is pretty easy to setup), or i guess a virtual box :l.
On the linux partition/OS download unyaffs, or yaffs tools (whatever it is). Use that tool to decompile. You can also try mounting the image. Both would be done in terminal.
I tried to install an app, which is supposed to run on Linux, on Gtab which involves following steps
1. configure
2. make
3. make install
The first step runs fine. Second step returns "make: not found". I searched in Gtab and didn't find this command. Should this command be able to run in android?
Don't think you will be able to do that on android. The compilers you need to "make" won't be there.
If you want to, you can install a debian or ubuntu chroot environment on your tab [there are several guides online], install the build-essential package in your chroot, and finally compile your source, and run the resulting binary into the chroot.
Ernesto de Bernardis
N900 - Galaxy Tab 7"
I just upgraded my Laptop to Linux mint 17 cinnamon bu t i am not able to access my storage of my mi3 like that in windows.When i connect my mi3 to laptop only driver installation partion on mi3 appears(have attached screenshot) not the storage(In windows both appears).If you have solution please give it step by step ,i am new to linux
kaapro9 said:
I just upgraded my Laptop to Linux mint 17 cinnamon bu t i am not able to access my storage of my mi3 like that in windows.When i connect my mi3 to laptop only driver installation partion on mi3 appears(have attached screenshot) not the storage(In windows both appears).If you have solution please give it step by step ,i am new to linux
Click to expand...
Click to collapse
1) Install SDK and setup adb
simple script to setup sdk and adb on linux, tested on old version linux mint as im using Ubuntu 14.04 now http://forum.xda-developers.com/showthread.php?t=1459945
just in case the udev rules is not available on above link. http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
2) Add below code inside android 99rules
#Xiaomi
SUBSYSTEM==usb, SYSFS{idVendor}==2717, MODE=0368
3) Voila, u can now use mtp into linux
4) other than that, u can use ftp. It is built inside the mi file explorer and connect it using Filezilla or simply type the ftp host into web broser.
This How-To is best viewed in a web browser as many of the forum readers strip out the formatting.
The obligatory warning:
"I take no responsibility for what happens to your device if you follow this guide. Flashing with Odin carries risk no matter the platform/OS used. This procedure has worked multiple times with 100% success in the test environment detailed below. It should work for any device, but I can't confirm, so feedback please if it works for your device."
- 3DSammy
Test Environment:
This method has been successfully used to flash stock Samsung firmware to a Samsung Tab S 10.5 (SM-T800) tablet. The SM-T800 Knox counter was "0 0x0000" before the Odin flash and remained as "0 0x0000" after the Virtualbox Odin flash of the Samsung stock 4.4.2 firmware and subsequently a Samsung stock 5.0.2 bootloader.
Distro: Ubuntu 14.04
Virtualbox: v4.3.10_Ubuntu r93012 along with extension pack (scroll down)
Windows Virtual machines: XP with all updates applied and Win7 with all updates applied except IE 11 cumulative update
Odin: v3.10
ADB, Fastboot and drivers: 15 second ABD Driver install (maybe the best solution for MS-XP)
KIES3: Samsung KIES3 and download link
Samsung stock 4.4.2 firmware *(XAC - Canadian): T800XXU1ANF8_T800XAC1ANF5_HOME.tar.md5
Samsung stock 5.0.2 bootloader
Tablet model: SM-T800NTSAXAC (Tab S 10.5)
*Samsung device firmware
Configuring a MS-Windows Virtualbox VM to use with KIES3 and ODIN:
1) Install/Upgrade to the latest Virtualbox for your Linux Distro and make sure you have a matching extension pack
2) Install a Microsoft XP or higher OS from an ISO image or your DVD player via Virtualbox. ISO's can be downloaded but unless you have a valid license key it can only be used for 30 days, which may be all you need.
Note: make sure to configure the memory and disk space to match the minimum requirements for the Windows version, KIES3 and Odin
3) Install the extension pack in the new Windows VM
4) Apply all available Windows Updates in the new VM. This can take a very long time depending on the Windows DVD/ISO you started with.
5) Take a VM snapshot as you do not want to waste the set up time again..
6) For the VM to have access to the PC's USB devices your user account must join the "vboxusers" user group. You need root access
for this step. In a terminal session:
> echo $USER # This will display your user id if you are unsure
> FOOUSER # For example
> sudo usermod -G vboxusers -a FOOUSER # "FOOUSER" should be your user ID as this is only an example
7) Reboot Linux (that is what I did but a log out may work as well)
8) Connect your POWERED ON Samsung Device to the PC
9) Start Virtualbox access the new Window VM's settings and click on USB to get the USB filter list
Check both "Enable USB Controller" and "Enable USB 2.0 (EHCI) Controller"
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG_Android".
Click OK
Disconnect your Samsung device and power it off
Reboot your Samsung device into Download mode (button combination is specific to your model)
Connect the device to your PC
Open the Virtualbox USB pop-up again
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG Gadget Serial".
Click OK
Disconnect your Samsung device from the PC and reboot the device (button combination is specific to your model)
NOTES:
I never modified any of the internal USB filter values leaving them exactly like Virtualbox added them to the filter list
The USB filter list should look like the screen shot attached to the bottom of this post
You can ignore any scary warnings on your device when invoking "Download mode" as no device connection or downloads are occurring.
Both USB filters are required as the "SAMSUG_Android" works with KIES3 while "SAMSUNG Gadget Serial" works with Odin.
10) Start the Windows VM and log in
11) ADB, Fastboot and drivers:
At this point you can attempt to let Windows recognize and install the necessary drivers or you can download and install them yourself. See 15 second ADB installer.
NOTES:
Despite installing the drivers manually on Windows 7 the VM recognized and downloaded and installed the drivers a second time when I attached my SM-T800. The driver discovery, download and install took way longer than I expected but eventually completed.
With the XP VM I manually installed the necessary drivers with the 15 second ADB installer script
12) Download and install KIES3 and Odin per their web page instructions. The downloads can be done within the VM. XP may need Internet Explorer upgraded as some web sites no longer support old versions of IE. Upgrading in XP can be a major hassle. Alternately (recommended) download the KIES3 and Odin software outside of the VM and set up a Virtualbox share or use a network share that is attached to the VM. I found that you could not install the executable directly from the share but could after you copied the install file into a Window's directory such as "Downloads".
13) KIES3 validation:
Start the Windows VM and log on
Start KIES3
Connect your booted Samsung device to your computer
After a while (up to a couple minutes) the KIES3 should connect to the device
Check that the device information is accurate (e.g. Internal storage used value)
Attempt a backup but the first time un-check the item for backup up your apps as that can take a very long while for a validation test.
NOTE:
App backups will skip some of the apps, I have no idea why. This is not a fail condition. KIES3 highlights that condition.
Check if the backed up data is accurate, I like to check wallpaper, pictures, music ... etc.
14) Odin validation:
Start the Windows VM and log on
Start Odin (run as administrator)
Power off your device and disconnect from the PC
Reboot your Samsung device into the bootloader and start Download mode (button combination is specific to your model)
Connect your download ready Samsung device to your computer
After a while (up to a couple minutes) the Odin log should show that your device is connected
NOTE: At this point you can use Odin normally.
WARNING: Odin is powerful and can brick your device so read the Odin instructions carefully
As I do not own any Apple products, I could not test this Odin solution on a Mac but maybe someone can see if these instructions can be tailored to Virtualbox on a Mac. Steps 6 and 9 are the only steps unique to KIES3 and Odin use of a VM and are likely similar across both Linux and MAC in regards to Virtualbox's VMs.
Here is an article describing how to use cross-platform JODIN3 as an alternate to Windows and Odin. You may find it a viable alternative to the solution described above..
I hope this helps someone and if you have issues/successes please post in this thread.
Screen shots:
USB filter pop-up settings and required Samsung device (SM-T800) USB filters
Odin after successfully flashing the Samsung 4.4.2 stock firmware to a Tab S 10.5 SM-T800 tablet
Odin after successfully flashing the Samsung 5.0.2 stock bootloader to a Tab S 10.5 SM-T800 tablet
Sent from my SM-T580 using XDA Labs
This is a message for everyone who has been troubled with Odin and VirtualBox. It worked for me that way, but took some time and errors. Finally I found out that the connection in the VM can be established by first opening Odin and then connect the mobile phone in download mode to the VM which requires a click on "devices". Puhhh, took some time, but finally after a week I found that out.