Easiest way to try Linux on a RK3288 if you only have a Windows PC.
First check your bootloader version and if necessary flash the RK3288Loader_uboot_V2.17.02.bin (downloadable from 'https://drive.google.com/file/d/0B99O3A0dDe67Tm1nVjdncVBuaG8') to your device to allow SD card booting.
Next download and uncompress one of these images ('https://drive.google.com/file/d/0B99O3A0dDe67cU1ZSkoybEdPeTA' or 'https://drive.google.com/file/d/0B99O3A0dDe67XzBhYTRKS1BqTnc') and write the image to an SD card using 'Win32 Disk Imager' on Windows (or 'dd' on Linux).
Then just put the SD card into your device and turn on the power to boot up Linux.
Booting will give you a full Linux desktop. It will not affect your installed software as everything needed to boot is taken from the SD card so it will work even if the device is 'bricked'. As it provides effectively a generic RK3288 kernel and resource image, both wifi and/or sound may or may not work depending on your specific device. However you can then use the system to build a bootable SD card by following 'Running Android or Linux from an SD card on a RK3288 device' (see 'https://plus.google.com/+IanMORRISON/posts/22Vxc6Sr5Ei') or similar.
The default username is 'linuxium' and the default password is 'p'.
A root password can be set by entering 'sudo su -' and then 'passwd root' in a terminal window. You can expand the file system to utilise the whole SD card by entering 'echo -e "d\nn\np\n1\n139265\n\nw" | sudo fdisk /dev/mmcblk1' then rebooting and entering 'sudo resize2fs /dev/mmcblk1p1' to complete the resizing.
One other advantage is that this image also supports a Linux root file system (RFS) on USB. So if you want to try a different RFS all you need to do is download one and write it to USB and then make sure both the SD card and USB are inserted before connecting the power.
Related
Hi,
I want to swap files between my Mac and my HTC Magic without using a microSD card. Standard it doesn't do that and only the card shows up on my desktop. Is there a way to do this? My microSD card broke and part of my data was lost.I'm running a custom rom (Cyanogen). It's kinda urgent. Thanks!
You have to use adb:
adb pull /data data
and with apps2sd:
adb pull /system/sd sd
Do I use the terminal for this? I'm a bit of a noob
You have to install the androidSDK
Aah that's a pity because I'm in no way a programmer nor have I touched a single line of code, ever. Aren't there any GUI applications (either on my mac or for my phone) that makes this possible?
I have downloaded the android SDK and I started up 'adb' which opened the Terminal (on Mac OSX) and showed me a list of commands, and at the end [Process completed]. I can't type anything. Please again forgive my noobness.
I have the MyTouch 3G with the Cyanogen Recover 1.4.
I had the latest CyanogenMod 4.2.7 with no problems. I tried applying the Enoch theme 1.4.7 and it put my phone in a boot loop. I tried factory wiping. I don't have access to any of the cyanogenmod zip files on my SD card because the Cyanogen Updater doesn't put it on the root directory of the SD.
So is there a way to fix this? Get back to any build of the phone to work? Can I access the SD card if I connect it via USB to my PC? PLEASE HELP!!!!
dannyfal!
i don t know if I undersoot you fully.BUT>>>> sometimes the SD card plays crazy,or get dammaged easy.In case you see the files on a computer but your phone is unable to read them is no big problem.If your phone is in bootloader mode and stucked there,it is a bit bigger problem.Have you ever applyed the hard reset ???It helps a lot.After that the SD card recognized by the phone as memory card2.So the phone is looking for the simple name SD MMEMORY.Or sd card.This is just matter of time.You give a name ending sd crad.bat and you can erase this bad sector data.In this case you might loose the program and your important data with it.BUT>>> you save sd card,and other files on it.
If you can t make it work coz your phone is in boot loader modus,than you need professional help.And a new rom update.
helos * hopr helped somehow*
dannyfal said:
I have the MyTouch 3G with the Cyanogen Recover 1.4.
I had the latest CyanogenMod 4.2.7 with no problems. I tried applying the Enoch theme 1.4.7 and it put my phone in a boot loop. I tried factory wiping. I don't have access to any of the cyanogenmod zip files on my SD card because the Cyanogen Updater doesn't put it on the root directory of the SD.
So is there a way to fix this? Get back to any build of the phone to work? Can I access the SD card if I connect it via USB to my PC? PLEASE HELP!!!!
Click to expand...
Click to collapse
You can enable usb mode in Cyanogen's recovery image by connecting the usb cable, dropping in to the console and typing (without quotes) "ums_enable" move your ROM and when you're done "ums_disable"
then "reboot recovery" and reflash.
If you don't have a computer you can use the console to my the files.
mount /sdcard <- Mounts the fat32 partition
ls <- See what files/folders are in the current directory
cd nameoffolder < change directory
then once you're in the folder where the ROMs are stored (cm-update, I believe) you can either move or copy them to the root.
use 'ls' again to find the filenanme of the ROM you want to copy/move..
cp name-of-rom.zip /sdcard <- to copy the ROM to the root, or use 'mv' to move the file.
EDIT: I am an idiot. You're on a MyTouch so you can't use the console in recovery. In that case connect your phone to your computer (which has the sdk setup with drivers) and type the commands I stated about after 'adb shell'
When I connect my phone via USB to the PC, and copy some files in the SD card, I get to see them after a reboot... I suppose the actual SDcard and a is a simulation , and everything is inside the data.img file... probably... So file appear when there is a reboot and the img files is updated?
Is that so??
Is this usual behaviour, or a build-specific bug?
Is there a way to copy files to the USB card and see them without the need of reboot?
What will happen , if I split the SDcard to to partititons, any way to make the non-bootable one mount automatically...
i suppose part of what you're saying is true, at least i've experienced some of the problems you describe some of the time.
sometimes i would unmount/mount the card after completing the usb disk transfer session...sometimes i would have to connect it back to my desktop in usb disk transfer mode and run a file system check.
a combination of the above mentioned ALWAYS got things going for me...never had to reboot to see the new data. but i have sometimes had to reboot to see ANY data. this is because, occasionally, i have seen that the sd card sometimes just doesn't WANT to mount. but i see a BLANK /mnt/sdcard folder and unmount/mount doesn't get it going.
the reason i've mentioned the practice of disk-checking your android usb disk transfer is because you sometimes may notice "sd card could not be mounted due to errors", or "sd card mounted read only" and i have always found disk errors when i ran the disk check following these messages, and this subsequently leads to the card mounting correctly and fully usable after the disk transfer session.
so my process is:
0. start the usb disk transfer mode
1. read what i have to from the card
2. write what i need to into the card
3. disk check!
4. stop usb disk transfer mode
5. let android complete its remount and look out for errors in android's notification area.
6. if errors found, be prepared to return to step 2. see next steps for clarity.
5. connect the cable again and see if the data i wrote is still there using my desktop's file explorer.
6. if 5 is true, done, disconnect the drive and usb cable.
7. if 5 is false, disk check and repeat from 2.
my theory is: the reason why you see them on the next reboot is because android seems to force stronger and sturdier disk checks on reboot. this often brings back files that should have stayed there in the first place when you copied them to the card. however, i've found such files "recovered" by the android repair utility are often corrupted. i find microsoft's disk check on the desktop much more reliable. it seems to just nuke bad files and/or rename and move them to the "FOLDER.000" style folders in the root of the disk being checked. so this clearly tells you that your last mass-write operation to the card failed and needs to be re-done. step 2 it is! OR reboot and rely on android's reboot initiated disk check and risk carrying corrupted forms of files you just copied and thought were safe to carry!
how can I do the disk-checking?
Method 1
on your windows desktop, with the device connected in usb disk transfer mode, open my computer:
1. right click the usb drive and choose "Properties"
2. go to the "Tools" tab
3. press the "Check now" button
4. enable "Automatically fix file system errors"
5. disabled "Scan for and attempt recovery of bad sectors"
6. press button called "Start"!
view the summary and its log when the operation completes to see what problems were corrected.
Method 2
on your windows desktop, with the device connected in usb disk transfer mode, press "Windows"+R on your desktop:
1. type "cmd" (without the quotes!) and press enter
2. a "black" window will appear
3. type "chkdsk <DriveLetter>: /f" without the quotes!
4. replace "<DriveLetter>:" with your actual usb drive's letter followed by a colon, (e.g. "f:")
5. press enter
view the summary and its log when the operation completes to see what problems were corrected.
For all those who wanted to transfer all their applications into the SD cards by default on their Android 2.2 Froyo operating system, we will check out the same on how you can do it. Many users recently reported that they were unable to transfer the applications to the SD card despite making use of the tool called Apps2SD which is one of the popular applications to transfer all the applications to the SD Card but it has failed to deliver for some of those who have HTC Desire and many handsets it doesn’t support. Though there are many ways for increasing the memory space marginally if you want which can be done by clearing the cache memory from the “Managing Applications” option from any Android phone.
But the real memory increaser is the only one if you manage to store all the apps in your SD Card, so let’s check out the same on how you can push your all applications which are stored in the phone to the SD card of your phone effortlessly. Considering the fact that most of the Android handsets now run on a minimum of Froyo 2.2 version, many apps don’t provide functionality to directly store the same on the device’s SD card until and unless Application requests you to select the same. So, we will check out on by default how you can transfer all the apps directly to your SD Card.
Procedure to store applications in SD Card:
First and foremost, from your phone you will have to ensure that the USB Debugging is ticked which can be done by going to the Settings > Applications >Development > then tick both Allow mock locations as well as the USB Debugging options over there.
After this you will have to download and install the Android Software Developer Kit (SDK) on your computer and after that once you download it, you will have to extract the package to the folder and then from that folder just run the application which is named as “SDK Setup.exe” and then simply click on the install selected option which is just located on the right bottom of the screen and follow the on screen instructions.
Now, connect the phone with the computer with the help of USB cable after which the OS will prompt you to install the set of required drivers which are missing which you can install from the path android-sdk/usb_driver folder, please note that you should not mount your device as you will have to plug in the cable.
Next up, you will have to run the Command Prompt and then you will have to go to the path Android-SDK/tools folder. Please note that, in Windows operating system , the Command prompt can be started by either pressing Win + R from your keyboard or alternatively you can click on “Start” tab from the main home screen and then can choose “Run” option and enter in the string as “cmd” followed by enter to enter into the command prompt. After entering in the command prompt, you will have to type in as “CD android-sdk” to get into the file via command prompt.
Now, in the android-SDK/tools folder, just type in the command as “adb devices” after which you will be getting the serial number which will be starting with the “H”. After this you will have to enter the command as adb shell pm setInstallLocation 2.
That’s it there you go, you have now successfully configured your Android phone successfully to store all the applications into the SD card. But please note that all the applications installed on the memory card will also be unavailable to the system each time you mount your phone as a disk drive and also the application performance is always better when stored in the phone as it can render quickly and also can run better in the background. So, unless and until the memory of internal SD card is not full, it’s not recommended to go for this method as this may partially slightly slow down your phone.
So, all the core applications which you use more often should be stored in the internal memory and the ones which are less used should be placed in the memory card. Do let us know if you face any issues while configuring all the above commands. Just in case if at any point of time you are unable to configure or encounters with some sorts of issue then you will have to again follow the procedure from the start.
Or..other way is..use titanium backup to move apps from internal to SD..easy..
Sent from my GT-S5830 using XDA App
Thanks for the write up.. I was able to move a bunch of my apps to the SD card freeing up some much needed space.
Hi,
Since yesterday, i've been attempting to boot windows 10 on a sd card in order to try it without messing with the internal ssd. To do that I had to transform my sd card into a fixed disk in order to create multiple partitions, then i convert it into a gpt format and partitioned it based on microsoft recommendations, i used the dism command to apply install.wim image on the windows partition and bcdboot to create to boot files on the efi partition. Sadly after booting on the sd card, i've encountered a bsod saying inaccessible boot device.
Can somebody help me?
Thanks.
try to make windows to go on your sdcard. it's must work.
when normal windows booting, it unmount all usb devices.
windows to go specially created for working from usb storage.
Microsoft modified versions of their OS (Windows 8.1 and above) to detect whether :
1. They are Enterprise versions. No Enterprise means no booting.
2. They are running from "authorized" USB devices - They have a whole list of approved ones on their site.
That is why it doesn't boot. Once you get to the Windows Loading Circle Screen, it'll remain stuck there, spinning forever. I hope they change that soon with newer builds of Windows 10, though. Wasn't working till 9926. Windows 8 works though.