Related
Ok, so you have firmware v. 123099 and wanna have root access... no problem.
I have just succesfully downgraded mine, 123099 to RC7, and then loaded ADP1.1h.
QMAT public (free) version used to succesfully downgrade with WM device: qmat_424.zip, md5: 7f0ccd1b52072bc2a6d594393f2ce348.
Newer QMAT can create Goldcard only in paid version. Buy it or get the old one somewhere else (giyf). You won't get it here or from me.
Requirements:
- Micro SD card formated FAT32 (128 MB to 2 GB), Sandisc cards may not work (but worked for me).
and
- Connected Windows Mobile device (application unlocked)
SD Card:
- Format recommended
Code:
format F: /FS:FAT32 /A:4096
(Replace F: with your SD card reader drive letter.)
TESTED, WORKING
1. Insret SD card to WM device and connect it do desktop. WM has to be application unlocked.
2. Download QMAT (http://revskills.de/pages/download.html)
3. Start QMAT and select Hardware Forensics -> Generate HTC Goldcard
4. Select Dream from the list of devices, Click "Get SD Card Serial from WINCE Device" and then "Save Goldcard Image to WINCE SD".
5. Copy DREAIMG.NBH to the root of sd (UK - RC7 recommended for our DREA110)
6. Power off the G1, put the card inside, hold camera button and press power button
7. Press power button to start flashing
8. To apply HardSPL, root & upgrade: http://forum.xda-developers.com/showthread.php?t=442480
9. You don't need the GoldCard any more (HardSPL fixes it, you should be able to flash any image now). So format the SD once again or borrow to a friend to downgrade his G1.
Other way: No WM device needed, just Linux (or Cygwin, to use dd) and paid version of QMAT. However this may not work (incorrect sd card serial number read from G1).
http://forum.xda-developers.com/showthread.php?p=3368673#post3368673
http://forum.xda-developers.com/showpost.php?p=3387344#post3387344
Other way: Generate image for free and dd it to sd
http://forum.xda-developers.com/showthread.php?p=3542745#post3542745
Proof:
{
"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"
}
Thanks DeToX for the GoldCard idea.
http://androidforum.cz/hacking-rooting-českého-kontinentálního-htc-dream-vyřešeno!--t428.html
nice ooone thank you very much for this helppp i hope it will work, i will write in a few minutes wheater its working, or my g1 is bricked .
good to know
ive got a friend in CZ that has been waiting for a way to root his phone
will let him know,
thnx for this
This is great news, moneytoo you are the king !
I did some reading at the links you gave and I believe in theory instead of using a windows mobile phone for QMAT, you can create a HTC goldcard and distribute that image for any HTC Dream downgrade.
Nope that doesn't work
Can anyone confirm, that this methode is working ?
Hi,
Because of i dont have a windows mobile device i would be glad if someone could give a little more detailed version of the "hardcore" way... im not sure how to accomplish that way ... anyone ideas or more detailed howtos for patching withour the ability of creating a goldcard?
finran said:
Hi,
Because of i dont have a windows mobile device i would be glad if someone could give a little more detailed version of the "hardcore" way... im not sure how to accomplish that way ... anyone ideas or more detailed howtos for patching withour the ability of creating a goldcard?
Click to expand...
Click to collapse
Hi, read again.
Requirements:
- Micro SD card formated FAT32 (up to 2 GB), Sandisc cards may not work (but worked for me)
and
- Connected Windows Mobile device (application unlocked)
or
- SD card reader and other way of getting SD card serial number
2 way to do. first or second -- connect WMD or card reader to get serial no of card.
I have a Windows Mobile Device but only with SD Card support but no micro SD.
But as i read so far, the only thing you need the WM Device for is to dump the micro SD serial number. So we just need to find another way to read out the number from the G1 directly... ?!
Tuxguevara said:
I have a Windows Mobile Device but only with SD Card support but no micro SD.
But as i read so far, the only thing you need the WM Device for is to dump the micro SD serial number. So we just need to find another way to read out the number from the G1 directly... ?!
Click to expand...
Click to collapse
Get a microsd adapter. MicroSD cards are 100% compatible with SD hardware.
Yes it Works
I have downgrades my German RC33 to UK RTC7 with this method, It was very easy to create this HTC Gold Card. Next Step ist a custom Firmware.
In a linux enviroment, you can get the card id by looking at the /sys fs.
For example in android it's on path /sys/class/mmc_host/mmc1/mmc1:XXXX/cid
The same applies for every recent linux kernel.
My perl skills are a bit rusty but I'll try and port the perl goldcard image utility to official unix perl versions.
Hi all,
if i try it with QMAT, i get the info goldcard for newer device isn't implemented in this new version after clicking on save goldcard image to file
infl00p said:
In a linux enviroment, you can get the card id by looking at the /sys fs.
For example in android it's on path /sys/class/mmc_host/mmc1/mmc1:XXXX/cid
The same applies for every recent linux kernel.
My perl skills are a bit rusty but I'll try and port the perl goldcard image utility to official unix perl versions.
Click to expand...
Click to collapse
It seems it works even with android. But what do you do after you got the serial number?
kingzero90 said:
It seems it works even with android. But what do you do after you got the serial number?
Click to expand...
Click to collapse
you need it for the goldcard.img generation.
Well I'm trying a linux-only version now, let's see what happens.
i followed the 'hardcore way' (using the dream-keys in the pearl-script of course) but without success .... still getting 'not allow' at the bootloader.
i've used the sd cid from '/sys/class/mmc_host/mmc1/mmc1:aaaa/cid' and replaced the first byte with '00' (also tried it without replacing the first byte).
does anyone had success with the 'hardcore way' or is there any other way if you don't have a windows mobile device??? (qmat isn't working as mentioned earlier)
problems solving
If you have any problem with downgrade EU G1 try jabber conf
address: [email protected] ask for htcorbit,detox,pedro
or live enter http://live.jabbim.cz/muckl/muckl.html?conf_room=android-google
I tried the hardcore way in linux with the help of wine to run ActiveState Perl and generate goldcard.img. Used a card reader.
Formated with "mkfs.vfat -F 32 -S 4096 /dev/sde1"
Then run "dd if=goldcard.img of=/dev/sde bs=1 count=288"
Unfortunately it doesn't work also.
Can anyone verify that the /sys/class/mmc_host/mmc1/mmc1:XXXX/cid (csd?) holds the same card serial as the qmat method.
infl00p said:
I tried the hardcore way in linux with the help of wine to run ActiveState Perl and generate goldcard.img. Used a card reader.
Formated with "mkfs.vfat -F 32 -S 4096 /dev/sde1"
Then run "dd if=goldcard.img of=/dev/sde bs=1 count=288"
Unfortunately it doesn't work also.
Can anyone verify that the /sys/class/mmc_host/mmc1/mmc1:XXXX/cid (csd?) holds the same card serial as the qmat method.
Click to expand...
Click to collapse
edit: I *think* serial is the number you need, but I'm not positive about that. I recall from previous conversations I've had that the value that you read (cid/serial? don't remember which) from that location is actually backwards. You may try flipping it around and trying that. Worth a shot at least
infl00p said:
Can anyone verify that the /sys/class/mmc_host/mmc1/mmc1:XXXX/cid (csd?) holds the same card serial as the qmat method.
Click to expand...
Click to collapse
Just checked and those numbers are not the same, even when reversed.
Maldune said:
Just checked and those numbers are not the same, even when reversed.
Click to expand...
Click to collapse
could you please check if the id from qmat contains the number found under /sys/class/mmc_host/mmc1/mmc1:XXXX/serial ? thx!!
maybe we need to put together serial + oemid + manid or something like that ...
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?
So it has been a hectic few days for me as I had alas managed to wipe my system reserved partition thinking that installing android x86 as multi-boot would actually boot windows for me. Wrong!!! My first poor encounter was the fact that when I had installed windows it had created the system reserved partition as ntfs... I had not realized this when attempting to install android x-86 as multi-boot. I will tell you the result, when booting it would appear to go to grub, however instead it just booted the first menu on the list without hesitation and gave no menu at all. To remedy this I had to use the windows 10 usb i had created for my initial install. I am still not sure how i managed to get it to boot the first time I think it may have just been dumb luck. When windows booted up i went to Disk Management (right click the windows menu and select from the drop down) where I then proceeded to delete the system reserved partition and reformat it fat32. At this point I was satisfied that android would point the out the windows boot, boy was I wrong. After installing Android x86 (_64 8.1 r3) I finally achieved the grub menu boot correctly. I also noted that when installing android x86 the only way it gave me option to add windows to grub was if i had installed without formatting first. (this can be done a few ways including just reinstalling much the same way you would dirty flash a rom on a phone) or you could use a tool to format the partition such as gparted or a linux live cd/usb. I suggest ext4. Oh wait my nightmare hadn't finished yet... Android x86 install had no problems at all (select partition to install(ext4)... do not format... install grub... yes to windows... yes read write... and then reboot) on reboot windows was in the grub menu and I selected it... oops there is no operating system!!! Well that is unsettling... ( I managed to get back into windows using the install media) and not so sure how. At this point i notice that my system reserved partition was now sda 3) So my next objective was to create a boot record for windows which could have been done easily from windows had I considered using bcdedit tool for windows. But since i knew that the partition was sda 3 I figured I could just point the grub menu to the correct drive... again wrong (there was still no boot mbr on that partition *sigh) Well I found that when i went into command line from the windows repair tool it would say I do not have permission to fixboot... wow nice job microsoft... after doing a bit more research I learned that the newer builds give this error when attempting to fix boot. I found a video on youtube which helped me alot but took quite a while to download the older working repair tool(installation media) but his video was fairly well put together. link here (https://www.youtube.com/watch?v=lRCyb7FzWFY). I followed his guide and this time with the repair tool that he shared in the description of his video, I was able to perform the fixboot (bootrec /fixboot) however one of his commands required the copying of bcd to the system reserved partition. The copy failed, however at this time running all the other bootrec commands seemed to go fine. So I exited command and went to the automatic startup repair, which to my surprise worked perfectly... (after a whopping 30 some hours of pulling my hair out of my head over this mess) And windows began to boot. At this point I gave my thanks to the poster of the video and shared my experience with his video in the comments below.) Now When windows booted up I downloaded the bcdedit tool. Personally I used the multi boot tool from this site (https://www.boyans.net/dual-boot-repair-windows-10.html) and selected repair mbr and boot record. This fixed my boot issue windows would boot normal at reset. However now my android was gone but thats okay.
At this point I just reinstalled the android x86 again over the same ext4 partition without formatting and added the windows to grub. This was perfect however when selecting windows did not boot. To fix this I had to edit the grub menu.lst and change the drive from hd(0,0) to hd(0,2) to point to the fat32 partition which had been somehow displaced to sda3. In order to do this I ran android in debug... when debug is running just hit enter and it give you a prompt... from prompt type without quotes "cd /mbr/grub" when the next prompt comes up you should be in the grub directory where the menu.lst is. Now type without quotes "vi menu.lst" this will take you into a text editor (note you can also change your monitors and resolution permanently in grub menu this way) using the arrow keys navigate to the line you want to edit, in my case the last entry which was windows entry when you get to where you need to edit hit the "i" key this will allow you to now enter and edit the text. After making changes hit "esc" to save changes type ":w!" then hit enter. To exit type ":q!" this will take you back to prompt. Now reboot your system and finally the results I had originally hoped for a multi-boot system with windows 10 and android. Now if you are attempting to do this and are looking for a guide to install I will make this just a little longer to make sure you dontt make the same mistakes I made.
1a) before you attempt to install a dual boot with grub... make sure your system reserved partition is fat32 if it is not you need to change it to fat32. as grub will not boot on ntfs partitions.
1b)you will need to have a blank partition, if you have spare room on the drive you can shrink your volume and create a new one. There are plenty of tools out there to format ext4 even from windows. Make sure you format it before installing. (if you are lazy like me you can format ext 4 from the installation, but there is a chance that you would need to reinstall again and choose not format to get the windows entry in grub)
1c)once your partitions looks the way you need and you have a working fat32 system reserved partition you are ready to move on. ( If you have to change a ntfs partition to fat32 I highly suggest you dont install anything until you have repaired the boot menu and tested it first to make sure it works)
2)create your install media... I prefer to use rufus as it is quick and easy, and I prefer the official android x86 as the 8.1 r3 is stable and works great, you can use whatever image you want though, lord knows i test newer versions as they come out. when you have rufus and the android x86 iso of your choice load rufus select your usb drive and select the iso with the browse button. then just hit start allow it to format and when it is done you can boot into your usb
3)To boot into your usb you may actually need to edit your bios and enable virtualization and make sure safeboot is not enabled, also you need a uefi system for x64 distros so if you have an older legacy bios you will need the x86 version instead or the system wont boot
4)When you finally get it to boot you will find the menu to use it as a live cd or install, select the install.
5a) You will now be asked where to install to. Pick the ext 4 partition you created for it.
5b) Now it will ask you to format choose do not format (again if you hadn't formatted the partition ext4 you may do it now, but you may have to reinstall and not format the next time to add windows to the grub menu)
6) You will now be asked to install grub answer yes, if you do not answer yes you wont be able to get back into your android partition again until you do.
7) Now it will tell you that it found a windows partition and asks you if you want to add an entry, select yes... if you do not you will have to make your own grub entry to get back into windows later or completely delete grub from the partition later.
8) Finally it will ask you if you want to make the system read write... select yes, if you select no i can not guarantee you will be able to install anything inside of the system.
10) The end... Installation finishes but do not click launch... instead click reboot. The reason for this is that I have noticed if you launch at the end of installation the grub somehow manages to disappear and you end up having to completely start over.
Enjoy your android x86 / windows multi-boot system.
make sure your system reserved partition is fat32
Click to expand...
Click to collapse
There is no system reserved partition on my laptop since I have a UEFI laptop.
Should I proceed ?
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
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
what is the file format of the one file that didn't moved?
aiSanaul said:
what is the file format of the one file that didn't moved?
Click to expand...
Click to collapse
it is Mp4, and was a video taken by me with the camera app
METAL66 said:
it is Mp4, and was a video taken by me with the camera app
Click to expand...
Click to collapse
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.
METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
what tool used to tranfer?
the Microsoft MTP protocol is not implemented well. in case you faced the famous data loss on copy with Windows Explorer, the files are gone and can't be recovered.
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
open cmd.exe and navigate to the platform-tools directory. type adb devices and confirm the connection on phone screen. you are now ready to copy directories.
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera
aiSanaul said:
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.
Click to expand...
Click to collapse
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
jwoegerbauer said:
what tool used to tranfer?
Click to expand...
Click to collapse
a normal copy paste from the phone "folder" on pc windows
alecxs said:
...
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
....
Click to expand...
Click to collapse
IMO a bad general recommendation, if phone isn't a Google device like Pixel or Nexus. One have always to use the ADB provided by device's OEM.
Right, Windows might complain "We couldn't find driver software for your device" even though you pointed it to the correct driver. But the driver is pretty generic and works for all devices, if you force install it.
Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> android_winusb.inf -> Android ADB Interface
It may not work for every device (I remember once a Sony Xperia didn't work) but I can confirm for Huawei, Samsung, Xiaomi, Cubot and Blackview devices. For which phone/ tablet the Google USB driver did not work for you?
But right, you can always use the OEM usb drivers for adb. There the PID/VID is added in the android_winusb.inf and driver is properly signed, so these drivers can installed automatically when device is connected. But I am not that Windows expert.
METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
Note that the MTP protocol is only a transfer protocol for copying files to/off the phone, it's not really a "drive" you can use like other disk drives from Explorer (for example editing files). It has issues with large files, I do not recommend that method. People have lost data trying to move directories from phone to PC due a serious bug.
adb is much more stable and faster, although it also cannot handle read errors in case of file system corruption on the phone itself. for this I recently wrote a shell script to pull files in smaller parts. But it requires Linux.
alecxs said:
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera
Click to expand...
Click to collapse
Huh? Why the -a?
-a listen on all network interfaces, not just localhost
MTP is bogus, ADB is much better.
I have a Windows utility adbsync (in the sig) that's nice for syncing directories between device and desktop.
I set it up to sync reading materials to devices and photos/movies back to desktop.
the -a flag for adb pull preserves mtime of pictures.
alecxs said:
the -a flag for adb pull preserves mtime of pictures.
Click to expand...
Click to collapse
Oh! I learn something every day.
Still, that's wacky that there is the global -a and the pull-specific -a.
(adbsync preserves the modified times too!)
METAL66 said:
a normal copy paste from the phone "folder" on pc windows
Click to expand...
Click to collapse
If MTP doesn't work as expected, then instead of using ADB try FTP: Windows OS has it - you simply have to activate the FTP client, Android file explorers as https://apkpure.com/file-manager-file-explorer/com.alc.filemanager have it - the FTP server.
METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...
METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
A file only can be read by system if both its start address and its end address ( there may be a chain of several start and end addresses if file is stored in chunks ) on the storage medium is known. The file's content hereby is irrelevant, it's not interesting the system what is to be read: that's only of interest when file's content should get viewed.
This should be clear to anybody. @alecxs has already pointed out that.
If a copy operation fails it should be obvious that the 1 file you mentioned couldn't get read by system, then it's corrupted for whatever reason.
You have no chance to get this fixed.
From the point of view of the computer reading and viewing a file are totally different things.
aiSanaul said:
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...
Click to expand...
Click to collapse
If a SD-card is locked
{
"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"
}
then you will not be able to modify or delete the contents on the memory card: READING a locked SD-card can't get prevented, never. If a SD-card isn't readable then it's corrupted. Point.