Hi Everyone,
My name is Andrew, and I am a bit of an Android n00b.
This week I tried to install the 2.3 Gingerbread leak on my Droid X.
I used the Droid bootstrap to install the Gingerbread from my SD card.
I wiped my cache and factory reset everything first.
LONG VERSION:
However, when I try to boot it, I get stuck on the Motorola logo.
The good news: I can boot into the boot-loader and recovery mode, but I can't do much from there, as "factory reset" option doesn't fix the ROM.
More bad news: Although I copied the contents of my SD card to my Laptop, my friend accidentally broke it. I'm currently SD card-less right now.
SHORT VERSION:
- Boot-loop on Motorola logo after attempted Gingerbread install
- Stock SD card broken
- SD card pre-wipe data saved on laptop
- Able to access recovery mode and boot-loader
QUESTIONS:
1. Will buying a new (generic) micro SD card fix my broken SD problems? If so, is there compatibility issues with SD card storage sizes? (e.g will a 32gb SD work, because my stock SD was 16gb)
2. Is it possible to get a ROM (Stock Froyo, Gingerbread, or Custom...) onto the droid?
3. If I just tell Verizon that I tried to reset my droid X to stock and it stopped working, does that void my warranty, and can they tell if I'm lying?
4. Does the missing micro SD card mess-up my warranty for the phone hardware?
5. If I can't get a ROM on there, is it possible for Verizon to via the boot-loader?
I haven't been able to find a problem quite like mine that has been resoleved.
If you know of (a) thread(s) that answers these questions, please link them!
Thanks SO much to any Android 1337 H4X0RZ who respond.
Sorry for this being so long!
Thanks again,
Andrew (AMcKeeCT)
AMcKeeCT said:
Hi Everyone,
- Boot-loop on Motorola logo after attempted Gingerbread install
- Stock SD card broken
- SD card pre-wipe
1. Will buying a new (generic) micro SD card fix my broken SD problems? If so, is there compatibility issues with SD card storage sizes? (e.g will a 32gb SD work, because my stock SD was 16gb)
Should do. just make sure that it is a reputable one (not from ebay)
2. Is it possible to get a ROM (Stock Froyo, Gingerbread, or Custom...) onto the droid?
If motorola provide some rom.utitity than maybe
3. If I just tell Verizon that I tried to reset my droid X to stock and it stopped working, does that void my warranty, and can they tell if I'm lying?
They will know in that state if u have clockworkmod
4. Does the missing micro SD card mess-up my warranty for the phone hardware?
Doubt it
5. If I can't get a ROM on there, is it possible for Verizon to via the boot-loader?
At a cost since ur warantee is void
Andrew (AMcKeeCT)
Click to expand...
Click to collapse
Sorry re lack of knowlage (never owned a motorola) note these are guses. They may be wrong and you are responsible for what you do to your device
Sent from my GT-P1000 using XDA App
Basically I don't have and won't have a SD card in the nearest future and do want to root and potentially switch to custom ROM. Do I absolutely must have a SD card for that or will internal "hard drive" (yes, I know it's not HDD) of Transformer will suffice? As far as I understand there's no data wiping involved in root or reflash process.
so far i don't think cwm can see the internal memory.
so you need a sd card to flash
or i may be wrong.
Thanks for the reply. Will just be patient until I get a microSD card then.
Just realized that I posted on a different account Just switched to my regular nickname.
I might be wrong but the NVFLash method does not need a micro sd card.
It's flashing from CWM that need it.
If I understand correctly nvflash doesn't support Prime One Seven (dumb keyboard not only lags but won't type numbers).
SteamTrout said:
If I understand correctly nvflash doesn't support Prime One Seven (dumb keyboard not only lags but won't type numbers).
Click to expand...
Click to collapse
Here's NVFlash 1.7. Don't ask me if it work or not I don't use NVFlash method since I've root.
http://forum.xda-developers.com/showpost.php?p=16420102&postcount=218
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Basically what I'm trying to do is get a 128GB SDXC card recognized in a Verizon Galaxy S3 [(via SD to Micro SD cable (NOT OTG)].
However it comes up as Blank SD card or unsupported format.
It reads perfectly fine on my HTC Thunderbolt running ROM version "liquid.mecha.20111118.145810" with "imoseyon-6.2.1AOSP" kernel.
Also reads perfectly on HTC Sensation running PARANOIDANDROID
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
ROM's Tried:
- Stock VRALG1
- Stock VRALF2
- Stock Root VRALHD DE-ODEX
- Stock Root VRALHD ODEX
- Incubus26jc_JellyWiz_VZW_10_10_12_RLS9_Note2_Edition
- Liquid-JB-v2.0-RC4-d2vzw
- Bean's Custom Stock Rom Build 14
- CleanROM 2.5
- CleanROM Ultra Lite Edition
- cm-10-20121005-NIGHTLY-d2vzw.zip
- PARANOIDANDROID 2.18
- Slim Bean 2.6.0
- Synergy Oct-03 0416_r73
All comes up as Blank SD card or unsupported format.
Here's a picture of the thunderbolt and the cable. It runs into the MicroSD card slot in the back of the phone.
(Since I can't add pictures yet due to post count, just add http in the beginning)
://imgur.com/LG2vA
://imgur.com/tG4yt
I sure hope it's not a limitation just on the S3 itself.
I'm going to go back and try different ROMs on my thunderbolt to see if it's related to a specific ROM or kernel, then probably proceed to testing different phones.
However any type of feedback is greatly appreciated :fingers-crossed:
Bump
Great effort! I hope you'll keep us posted on your progress.
Perhaps Samsung is intentionally blocking cards larger than 64GB on these phones. Have you tried apps such as NTFS mounter and tried mounting the card with other file systems such as NTFS/EXT3/4 etc? Maybe this will get around any space restrictions that Samsung may have imposed on the Android file system. But it seems like you already have.
Perhaps this thread may help out as well:
http://forum.xda-developers.com/showthread.php?t=1797499
It would be interesting to see what SDXC controller the S3 uses. If it is the same as on a phone where the 128GB card works perhaps it may be possible to patch the S3 with the driver in the other phone.
You should try different kernels, not ROMs
g00ey said:
Perhaps Samsung is intentionally blocking cards larger than 64GB on these phones. Have you tried apps such as NTFS mounter and tried mounting the card with other file systems such as NTFS/EXT3/4 etc? Maybe this will get around any space restrictions that Samsung may have imposed on the Android file system. But it seems like you already have.
Perhaps this thread may help out as well:
http://forum.xda-developers.com/showthread.php?t=1797499
It would be interesting to see what SDXC controller the S3 uses. If it is the same as on a phone where the 128GB card works perhaps it may be possible to patch the S3 with the driver in the other phone.
Click to expand...
Click to collapse
Glebun said:
You should try different kernels, not ROMs
Click to expand...
Click to collapse
Thanks for the suggestions.
Yes I already tried using NTFS mounter with all the other file systems, nothing was being detected or coming up at all. Maybe NTFS mounter is targeted more towards OTG connection, not too positive on that one.
I forgot to mention I did try different kernels. Whichever came with the ROMs and including KT747, Lean, and Trinity (also the variants with touchwiz and AOSP).
I've also gotten around to testing the Samsung S3 variants on T-Mobile, AT&T, and Sprint... None of them detected the card.
However a friend of mines lent me his Korean variant S3 (SHV- E210S with Exynos) and that phone detected the card perfectly fine.
Phones that also were tried were: LG Spectrum, Galaxy S2 (International), myTouch 4G. All of them detected the card even in recovery.
*I don't believe it's kernel related, if all the other phones were able to detect it in recovery...
I also contacted Samsung via e-mail but they weren't much supportive on the whole topic. Just a simple answer of the Galaxy S3 was never meant to support anything above 64GB (in which I find that untrue with the Korean variants at least).
I'm about out of ideas on what left there is to try... hopefully someone can come up with something.
I really liked the S3 but having a 128GB memory card sitting around would be a waste.
Going to test on my friends Note II since Verizon is going to be getting their own also, then will probably just ships.
Hopefully my information has helped someone.
Have you tried a small capasity SD card to see if it has to do with the connection or if it has to do with the size?
kris333 said:
Have you tried a small capasity SD card to see if it has to do with the connection or if it has to do with the size?
Click to expand...
Click to collapse
I believe it would just be the size issue on the S3. 64GB SDXC works fine. 128GB does not.
Shouldn't have anything to do with card or connection if it worked on 5+ other phones.
BattousaiJimmy said:
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
Click to expand...
Click to collapse
I am very interested in the outcome of this
Getting a 128Gb SD card working in the S3 would be awesome!
Have you tried 2 64Gb FAT32 partitions? or maybe several smaller partitions.
Maybe even just a single 64Gb partition
My 2c
Ben
Has anyone figured this out? I just bought the converter and a 128GB SDXC card. At first I was on the TW Jellybean K3 11B ROM I hooked it up without formating and the ROM recognized it as 120GB. So I plugged it into my PC to throw some files on it some ROMs and back ups etc, then I put it back in my phone went into recovery to flash a ROM that I put on the card and it was taking forever? As if the converter cable was slowing down the speed? So anyways I ended up flashing a aosp ROM of of my micro SD card (Carbon 4.2.2) then I plugged my converter with the 128gb card back in but the ROM wouldn't recognize it? So I tried formatting it in recovery and on the ROM but I'm still having no luck?? Any Suggestions or ideas how to get it to work? Thanks!
Sent from my SCH-I535 using Tapatalk 2
If you will scroll down or search, there is already a thread on this and the OP got it to work. The name of the thread is "Will this give me more memory?"
HHF2 said:
If you will scroll down or search, there is already a thread on this and the OP got it to work. The name of the thread is "Will this give me more memory?"
Click to expand...
Click to collapse
Yea that's my thread. I found this thread trying to get my phone to recognize my SD card?
Sent from my SCH-I535 using Tapatalk 2
My bad, I didn't pay attention to the usernames since I thought yours was working.
BattousaiJimmy said:
After quite a bit of researching + trial and errors, I'm kind of stumped on this one...
Basically what I'm trying to do is get a 128GB SDXC card recognized in a Verizon Galaxy S3 [(via SD to Micro SD cable (NOT OTG)].
However it comes up as Blank SD card or unsupported format.
It reads perfectly fine on my HTC Thunderbolt running ROM version "liquid.mecha.20111118.145810" with "imoseyon-6.2.1AOSP" kernel.
Also reads perfectly on HTC Sensation running PARANOIDANDROID
Steps I've tried:
- Format Card: fat32, ntfs, exfat, ext3, ext4 (via EaseUS Partition Master) - Comes up as Blank SD card or unsupported format.
- Also tried all available allocation unit size for fat32 - Still the same thing
- Tried formatting on the S3 itself - Still the same thing
- Tried formatting on the Thunderbolt and transferring the card over - Still the same thing
ROM's Tried:
- Stock VRALG1
- Stock VRALF2
- Stock Root VRALHD DE-ODEX
- Stock Root VRALHD ODEX
- Incubus26jc_JellyWiz_VZW_10_10_12_RLS9_Note2_Edition
- Liquid-JB-v2.0-RC4-d2vzw
- Bean's Custom Stock Rom Build 14
- CleanROM 2.5
- CleanROM Ultra Lite Edition
- cm-10-20121005-NIGHTLY-d2vzw.zip
- PARANOIDANDROID 2.18
- Slim Bean 2.6.0
- Synergy Oct-03 0416_r73
All comes up as Blank SD card or unsupported format.
Here's a picture of the thunderbolt and the cable. It runs into the MicroSD card slot in the back of the phone.
(Since I can't add pictures yet due to post count, just add http in the beginning)
://imgur.com/LG2vA
://imgur.com/tG4yt
I sure hope it's not a limitation just on the S3 itself.
I'm going to go back and try different ROMs on my thunderbolt to see if it's related to a specific ROM or kernel, then probably proceed to testing different phones.
However any type of feedback is greatly appreciated :fingers-crossed:
Click to expand...
Click to collapse
I believe it may specifically be a limitation of the Verizon s3 version. I have a 256gb card working fine on an att Note 2, and att and tmobile s3s have been proven to work as well.
Is it possible on the surface pro? Im a developer/student. Windows 8 is great for in class stuff but when it comes to developing, linux takes the win. I'd love to be able to install linux on a microSD card and boot to that (yeah, I know it will be slow but it can be left in the surface without protruding too much). Anyway is this possible? I can't find anything on this beyond removing win 8 and loading linux on it.
Meh, kids these days... when I was in college, I tri-booted on a 60GB hard disk.
But, if the internal storage isn't good enough for you, yes of course you can install Linux to the microSD card. You'll need to disable Secure Boot as usual for installing Linux at all. Beyond that, it's the same as any other Linux install except instead of reformatting the system partition, you reformat the microSD card and install there. People have been installing Linux to removable storage for years; it's no different on the Surface Pro and a microSD card than on a desktop with an external HDD or a laptop with a flashdrive or ... you get the idea.
Great, Thanks. I was just unsure since no one has seemed to do it (or at least posted it on the internet).
And don't get me wrong, I remember installing linux/windows on my first laptop with 20GB. These days, however, files are larger than CD's and the remaing space on the pro just does not cut it anymore, unless I want to delete all my downloads after using them.
Thanks again!
YOu need to go into charms > settings > Change PC Settings > General > Advanced startup to be able to boot from a usb or sd
can I install MAC OS? if I can I will order right away
seesunmoon said:
can I install MAC OS? if I can I will order right away
Click to expand...
Click to collapse
I think you asked the wrong question here.
Honestly, it does not matter if you can install MAC OS on the Pro.
The question you need answered is: Are there MAC OS Drivers for the Pro's Hardware? If not, then there is no point in seeing if the OS installs.
right, right, i guess apple will make something like surface pro, tablet with full max os
If history is any indication, they will do so 5-10 years after somebody else (typically Microsoft) has a similar OS/device, call it "revolutionary" and "innovative", and people will think they invented it...
Seriously though, I'm sure you could Hackintosh the Surface Pro, but hardware support may be lacking. The basic stuff (video, storage, sound, probably USB) and possibly some other things like WiFi and webcam will probably work. Touch and stylus are highly questionable. Normally I'd say that there's no chance of the covers working, but apparently they're fine under Linux so maybe they use an electrically standard interface through that funny docking connector.
There's something very weird about buying a (primarily) software company's hardware to put a (primarily) hardware company's software on it, though...
I have no doubt the Hackintosh guys will be all over this once a few of them get an S-Pro, I had an XE700 and there were people running it on them so I cant see the Pro taking much time for them to jump on to it.
Cool Dude
GoodDayToDie said:
Meh, kids these days... when I was in college, I tri-booted on a 60GB hard disk.
But, if the internal storage isn't good enough for you, yes of course you can install Linux to the microSD card. You'll need to disable Secure Boot as usual for installing Linux at all. Beyond that, it's the same as any other Linux install except instead of reformatting the system partition, you reformat the microSD card and install there. People have been installing Linux to removable storage for years; it's no different on the Surface Pro and a microSD card than on a desktop with an external HDD or a laptop with a flashdrive or ... you get the idea.
Click to expand...
Click to collapse
This does really answer the question at hand,
I haven't yet been able to boot from an MicroSD card I have used a USB drive to boot into Ubuntu 14 Trusty Thar, using instructions that are all over the web, however I haven't found any documentation of successfully boot from a MicroSD card. I will be trying this afternoon and will post what I find. Installing linux to the microSD card I'm sure will be straight forward, its the booting that will be an issue I'm sure.
Follow up coming soon
n4m4st3 said:
This does really answer the question at hand,
I haven't yet been able to boot from an MicroSD card I have used a USB drive to boot into Ubuntu 14 Trusty Thar, using instructions that are all over the web, however I haven't found any documentation of successfully boot from a MicroSD card. I will be trying this afternoon and will post what I find. Installing linux to the microSD card I'm sure will be straight forward, its the booting that will be an issue I'm sure.
Follow up coming soon
Click to expand...
Click to collapse
I got this to work. You need to use:
rufus.akeo.ie
And then just choose USB boot from the menu advanced start up options menu. Which is funny because it doesn't actually show the micro sd as an option to boot, but it automatically finds it somehow.
Pretty sure the uSD slot is attached via USB, so it's basically just "boot from USB external storage".
Another way you could have done it is to install the Linux bootloader (GRUB stage 1) to the internal storage, and then have that chainload to the uSD card. That should work even if for some reason the firmware doesn't want to boot off uSD normally.
I just got a Surface Pro 2 and started playing with the idea of booting Linux off the SD card. I haven't done an actual installation yet, but I was just playing with the idea of making a bootable USB device preferably without having to change the internal SSD. (Especially since I have the 64GB base model and that's really barely enough for a comfortable use of Windows. I also wanted to leave the recovery partition intact as a good just-in-case.)
So first I made a bootable generic USB flash drive using UNetbootin and a stock Ubuntu 14.04 desktop installation image. Works as expected, can go into the "Advanced Startup" screen and boot from USB device. Nothing special, was able to launch the live session.
Then I used UNetbootin again, this time on an 8GB microSD I had laying around. The Surface would NOT boot off the microSD card through "Advanced Startup."
Then I tried it using the Rufus tool linked above -- this worked. You can go through "Advanced Startup" or hold volume down when powering on the Surface. Either way will launch the Live session. Very cool.
So then I went back and tried to figure out what was different. Same card, same base ISO... what I noticed was that Rufus was setting the "lba" flag on the SD card's FAT32 partition. So I formatted and recreated the card with UNetbootin again, verified it was unbootable, then used gparted to set the "lba" flag. After that, it booted. So this is something to note.
I'll have to actually try installing to the card and seeing if the Surface will boot from it or not. But this is something at least.
EDIT:
It seems like Surface will never boot the SD card if it isn't exactly a single FAT32 partition consuming the entire microSD card.
I'll just wrap up my last bit of contribution to this for now. I used a virtual machine with an EFI install of Windows 8 to stage this at first...
So the short end is, it seems the Surface Pro's firmware is strict about what it will boot from USB, and it seems to be a device that must be a single FAT32 partition with the "boot" and "lba" flags set, or else it won't work. If anyone knows of another combination, great, but this is what I determined through my limited experimentation.
Basically the most minimally invasive Ubuntu (or other Linux) install I could think to do that generally leaves the Surface a Surface and a Linux device second was this procedure (using Ubuntu 14.04):
Create an Ubuntu USB install device (use the aforementioned Rufus tool for best results or else be aware of the partitioning specifics.)
Use "Advanced Startup" or "Vol -" at power on to boot the USB key
When installing and prompted about disk installation, do "Something Else" (Careful! Very easy to obliterate the internal Windows or reduce space on less-equipped Surfaces to useless levels!)
Use "/dev/sda" as the place to install the boot loader (GRUB)
Resize the Surface's main Windows partition back by a small amount (e.g. 512MB)
Create an ext4 partition in this space and set this as the "/boot" mount point (exercise to the reader to look up making a /boot partition for GRUB and deciding on the amount they want to allocate)
Partition your SD Card in the Surface however you like, but you'll need some kind of ext4 partition for the Ubuntu installation, of course! (e.g. I split mine into NTFS, ext4, and swap space, but you can do whatever suits you)
Set your root mount point on the SD Card's ext4 partition.
And that's pretty much it -- the Ubuntu installer is smart enough to take care of the rest.
Major point here, regarding step 4 -- you CAN have the "/boot" on your SD card if you like, but what will happen is that you will be unable to properly boot from GRUB if you don't have that specific SD card inserted. If you never plan to remove your SD card, you can avoid changing the internal memory partitions at all.
Installing GRUB to the SD card through the Ubuntu installer will do no good since, again, the Surface seems adamant about only booting a device with a single FAT32 partition occupying the full space. Obviously the installer USB device you make IS a bootable Linux image on a FAT32 partition, so you CAN pull it off if you have all the know-how -- i.e. setting up GRUB and booting an ".img" file from the FAT32 partition -- pretty sure the Ubuntu installer doesn't support this in a straightforward manner.
In any case, I'm happy with GRUB and "/boot" being on /dev/sda. I can remove the card and simply be unable to boot Ubuntu, but still use Windows. If you follow this installation, I highly recommend setting GRUB to boot Windows by default just in case you do remove the SD card and don't have your touch cover connected. Further, I recommend setting up GRUB so that it always times out (on the default Windows selection) even if the previous boot failed (which, by Ubuntu default, GRUB will not timeout on a failed boot.) But of course this is all user preference and what kind of situations you expect yourself to be in.
Hopefully this is at least one adequate answer to the OP, even though it is over a year old.
Footnote: Haven't gotten the built-in WiFi / Bluetooth working, even with putting the firmware in place. (The mwiflex driver is complaining about a command timeout as soon as it loads and does not progress.) Tried a newer kernel, still doesn't work. I'm mostly interested in the WiFi, but as yet, still no good. But that's beyond what the OP was strictly asking.
UPDATE: Firmware update fixed WiFi. (Info from https://bugzilla.kernel.org/show_bug.cgi?id=64111) -- Basically clone git git://git.marvell.com/mwifiex-firmware.git and copy /mwifiex-firmware/mrvl/usb8797_uapsta.bin to /lib/firmware/mrvl and reboot. Not sure if newer kernel needed. Was running kernel 3.15.0-999-generic from Ubuntu's mainline.
why install grub? the only reason is if you want to default boot into windows
since you're installing a second os on the microsd, you can access it directly with power+vol down
anyways, i was brought here because i was thinking of getting an sd card with a fully independent os for my surface pro
if i burn a ubuntu iso onto the microsd, you wouldnt actually be installing the os onto the sd card right? every time you boot, it would be the live-cd ubuntu
is there a way to install the full os onto the microsd?
anonxlg said:
why install grub? the only reason is if you want to default boot into windows
since you're installing a second os on the microsd, you can access it directly with power+vol down
anyways, i was brought here because i was thinking of getting an sd card with a fully independent os for my surface pro
if i burn a ubuntu iso onto the microsd, you wouldnt actually be installing the os onto the sd card right? every time you boot, it would be the live-cd ubuntu
is there a way to install the full os onto the microsd?
Click to expand...
Click to collapse
Just install ubuntu onto the microsd...
anonxlg said:
why install grub? the only reason is if you want to default boot into windows
since you're installing a second os on the microsd, you can access it directly with power+vol down
Click to expand...
Click to collapse
With power+vol down, I was only able to boot a USB device or microSD that was partitioned exactly as a single FAT32 partition occupying the entire device, which is also what you get from making a bootable Ubuntu key using tools usually. Even if all I did was shortchange the FAT32 partition, the Surface would no longer try to boot from it. It would not boot an SD card I installed Ubuntu to, and I tried it as a non-EFI and EFI install. If you have different results, go ahead and post about it. It seems to me that the firmware was being extremely particular about what kind of drive it was booting from. I'm not sure why Microsoft would make it so particular except to perhaps limit was sort of "recovery" devices you might be trying to load. Logically speaking, it only needs to boot a FAT32 partitioned device since that's the only thing generated by the recovery software in Windows 8, so they have no reason to support anything else.
Thank you southbird! Works great on my Surface Pro 2, BUT ....
Partitioned my micro SD (using gparted) as your instructions: two partitions - first partition ext4 and the other NTFS. Added small partition on internal HDD for /boot. I installed kubuntu 14.01. Made Windows the default boot, and everything works except Windows 8.1 will not recognize the partition for data (the partition that is formatted NTFS). It "sees" it as a broken drive and wants to format the whole micro SD card and I know it will delete the ext4 part (where / resides) because it doesn't "see" the card as being partitioned. Your instructions sound like you got the data partition to work (it is "seen" and usable in kubuntu). Did you do something else to get Windows to "see" it as a separate data partition? :fingers-crossed::fingers-crossed:
southbird said:
I'll just wrap up my last bit of contribution to this for now. I used a virtual machine with an EFI install of Windows 8 to stage this at first...
So the short end is, it seems the Surface Pro's firmware is strict about what it will boot from USB, and it seems to be a device that must be a single FAT32 partition with the "boot" and "lba" flags set, or else it won't work. If anyone knows of another combination, great, but this is what I determined through my limited experimentation.
Basically the most minimally invasive Ubuntu (or other Linux) install I could think to do that generally leaves the Surface a Surface and a Linux device second was this procedure (using Ubuntu 14.04):
Click to expand...
Click to collapse
Hello Guys!
I have another question to add here!
Next week i'll get my Surface Pro 2 with 256GB
The last days my mind played with some ideas to have a dualboot option in the surface.
Is it possible to install Android Lollipop (or Kitkat) x86 on the micro sd (64GB) and boot from it?
I have read the whole thread but its a lil bit complicated.
Would be nice if anyons can show this in a step by step process, or guide me to a tutorial.
thanks!!
Methisfaction said:
Hello Guys!
I have another question to add here!
Next week i'll get my Surface Pro 2 with 256GB
The last days my mind played with some ideas to have a dualboot option in the surface.
Is it possible to install Android Lollipop (or Kitkat) x86 on the micro sd (64GB) and boot from it?
I have read the whole thread but its a lil bit complicated.
Would be nice if anyons can show this in a step by step process, or guide me to a tutorial.
thanks!!
Click to expand...
Click to collapse
Indeed you can, however:
1. The microSD will need to be formatted with GPT partition scheme, and the boot partition must be FAT32;
2. The January 2015 UEFI update removes ability to boot from microSD. Skip that and you're golden!