I have an iBall Slide i701 running Windows 10. So, I wanted to try RemixOS on my tablet after seeing a thread on some site. So, I downloaded the zip and tried to use the USB option but my USB was not detected at all. I tried everything like formatting the pendrive to different formats, but still no luck. Then, I tried the Hard Disk installation, but here's the problem. My tablet has 16GB of internal storage of which right now about 7GB is free (which isn't enough to repartition). But, I do have a 16GB SD Card on the tablet but it's being shown as Secure SD Storage and I am unable to create a normal bootable partition with the SD Card. So, when I try the hard disk installation option, the SD Card doesn't show up among the hard drives, instead it shows among USB. Anyways, I tried USB installation to the SD Card, but it won't boot into the USB though I have set UEFI as boot option #1 and disabled secure boot.
Please help me out!
Well i have tried everything from booting linux to win7 win 8.1 installers with and without efi installers it just doesn't boot from any flash drive. There is a lock in the bios on boot option that forces it to boot from internal and yes i also tried via its sd slot, the prob is the sd card can only be accessed after it boots up, so thats a bummer,
vistatech9895927087 said:
I have an iBall Slide i701 running Windows 10. So, I wanted to try RemixOS on my tablet after seeing a thread on some site. So, I downloaded the zip and tried to use the USB option but my USB was not detected at all. I tried everything like formatting the pendrive to different formats, but still no luck. Then, I tried the Hard Disk installation, but here's the problem. My tablet has 16GB of internal storage of which right now about 7GB is free (which isn't enough to repartition). But, I do have a 16GB SD Card on the tablet but it's being shown as Secure SD Storage and I am unable to create a normal bootable partition with the SD Card. So, when I try the hard disk installation option, the SD Card doesn't show up among the hard drives, instead it shows among USB. Anyways, I tried USB installation to the SD Card, but it won't boot into the USB though I have set UEFI as boot option #1 and disabled secure boot.
Please help me out!
Click to expand...
Click to collapse
hello, ive had similar problems with the iball marvel 6 and ive contacted iball for it and they sent me this email
With reference to your below mail, iBall compbook Marvel 6 comes with pre-installed OS 64 bit Windows 10 Home Ver. Customer cannot Upgrade or downgrade the OS through online or with any other external devices. Compbook works on tablet technology it will not support any other OS except the OS which is preinstalled in it, therefore there is no any separate drivers available for that..
i dont know if this is similar to yours but your slide also works on tablet technology so it might be the crux of the problem.
It is possible to load from USB
I had the same problem with my iball i701, during win10 upgrade it went into blank screen of death. Heres what i did.
0. Make efi shell as first boot in bios.
1. Go into efi shell, type map. It lists the drives, usb is not listed.
2. Unplug usb, type map -r
3. Plug in usb drive (my usb was win10 efi bootable drive), type map -r
4. Voila now the last entry is usb drive.
5. Type reset, press esc to go into bios. Usb is now listed in boot options.
Done.
Related
I need to repartition my SD card for changing ROM on my HTC Desire. I planned on using GParted for the task, but so far I have failed to get the SD card to show up in GParted. What I have tried so far:
1. Plugging in my phone to my MacBook I can see my device and in Disk Utility both partitions show up (although obviously the ext4 won't mount).
2. Booted GParted in Parallels but the device won't show up
3. ...so I tried booting my mac with it, but still, the device won't show up.
4. Tried booting a PC off GParted. Still no device!
5. Plugging the SD card into a Samsung Galaxy S and tried the above again, still without success.
So problem persists, I cannot get the SD card to show up in GParted! Do you have any idea how to make it work?
Try to use card reader. I'm sure it can detect when you use it. I'm a fans of gparted.
Sent from my Nexus S using xda premium
Alright, then I need to rest my restless mind and wait for the holidays to pass so I can get hold of one! Thanks.
Hi,
When the (HTC Desire) phone is powered up it is unable to mount the SD card, and I am unable to have it mounted from the "Settings > SD card & Storage" menu. Having said that, the micro SD card can be accessed from a computer (when plugged in directly to the computer, i.e. no issue with the card), and moreover, when I am in the recovery mode, I can have it mounted and browse it. By the way, the card could be accessed from the phone until I downgraded the O/S, and managed to have it rooted.
When the phone is running normally, and connected to the USB port of a laptop, the laptop does recognize a device connected (can even do ADB), but I believe because the SD card is not mounted, the phone does not offer the option to make the card appear as a disk drive for computer access.
I am running the original (RUU, Telstra) Android 2.2 (2.26.841.2) on a HTC desire, after I had it "S-OFF'ed". After reloading the original 2.2, I had it rooted.
The micro SD card is a 2GB one, with approx 1.5GB formatted as FAT16 (contains typical file and photos), and 0.5 GB as EXT3 (contains nothing at the moment).
HBoot: 6.93.1002
S-Off (thanks to Revolutionary)
Recovery mode: ClockworkMod v5.0.2.0 (I manually loaded it)
I have searched online for solutions, and have not been able to have it fixed. Others seem to have different issues to that of mine. Usually, they cannot mount the SD-card at all (not even from recovery), or their SD card just needed to be reformatted. I think I have indicated that these do not appear to be relevant to my issue at all. I have also tried "Fastboot oem enableqxdm 0", and it made no difference.
I look forward to your kind responses and feedback.
Thank you for your attention.
desiremhtc said:
Hi,
When the (HTC Desire) phone is powered up it is unable to mount the SD card, and I am unable to have it mounted from the "Settings > SD card & Storage" menu. Having said that, the micro SD card can be accessed from a computer (when plugged in directly to the computer, i.e. no issue with the card), and moreover, when I am in the recovery mode, I can have it mounted and browse it. By the way, the card could be accessed from the phone until I downgraded the O/S, and managed to have it rooted.
When the phone is running normally, and connected to the USB port of a laptop, the laptop does recognize a device connected (can even do ADB), but I believe because the SD card is not mounted, the phone does not offer the option to make the card appear as a disk drive for computer access.
I am running the original (RUU, Telstra) Android 2.2 (2.26.841.2) on a HTC desire, after I had it "S-OFF'ed". After reloading the original 2.2, I had it rooted.
The micro SD card is a 2GB one, with approx 1.5GB formatted as FAT16 (contains typical file and photos), and 0.5 GB as EXT3 (contains nothing at the moment).
HBoot: 6.93.1002
S-Off (thanks to Revolutionary)
Recovery mode: ClockworkMod v5.0.2.0 (I manually loaded it)
I have searched online for solutions, and have not been able to have it fixed. Others seem to have different issues to that of mine. Usually, they cannot mount the SD-card at all (not even from recovery), or their SD card just needed to be reformatted. I think I have indicated that these do not appear to be relevant to my issue at all. I have also tried "Fastboot oem enableqxdm 0", and it made no difference.
I look forward to your kind responses and feedback.
Thank you for your attention.
Click to expand...
Click to collapse
Welcome to the forum.
I had the same problem once. The solution is very simple but annoying: Many Android phones are unable to mount SD cards formatted with tools like MiniTool Partition Wizard. Reformat the SD card using CWM (ClockWorkMod) recovery and everything will be fine.
Good luck.
It worked
nik10 said:
Welcome to the forum.
I had the same problem once. The solution is very simple but annoying: Many Android phones are unable to mount SD cards formatted with tools like MiniTool Partition Wizard. Reformat the SD card using CWM (ClockWorkMod) recovery and everything will be fine.
Good luck.
Click to expand...
Click to collapse
Dear friend,
Thank you so much for your simple tip. It worked! I felt so dumb for not trying it out myself. I guess I was tired of trying things without considering moving my data back and forth. Once more thank you.
AW: [Q] Phone doesn't mount SD-Card, but I can mount it in the recovery mode
desiremhtc said:
Dear friend,
Thank you so much for your simple tip. It worked! I felt so dumb for not trying it out myself. I guess I was tired of trying things without considering moving my data back and forth. Once more thank you.
Click to expand...
Click to collapse
Well, this IS annoying. I had the same problems and copied my data three times (~ 12 GB). So I can understand that.
Good evening,
I have also the same prroblem.
Is there any manual - instructions that I could follow in order to solve the issue with the CWM?
Thanks in advance.
Hi all.
Here's the situation:
I have a 32 gb Sandisk (unsure of the class) sd card I've used with 2 different phones for at least over a year now. I took the card out of my phone to connect it through my laptops built in card reader for the purpose of transferring large files (card reader speeds are much faster than usb mounting through the phone for me). When I put it in the computer Windows wouldn't recognize it. Now it won't mount in my phone at all, and it won't work correctly on my PC. When I connect it to my computer it says the card needs to be formatted before use, but then when I go to format it, it shows up on the Windows formatting screen as only having a 30.6 mb capacity and I get the message "Windows was unable to complete the format" whenever I try to format it, no matter the settings.
So my question is, how do I get the darn thing to work again? I think something must have happened between shutting my phone down to remove it and putting it in my computer. I just don't know what. Anyone else ever experience this? (I've already given up on recovering all of my files, but if it's possible to save them that would be amazing )
Things I've tried:
formatting via Windows
formatting via android
formatting /external_sd via Clockworkmod recovery
a couple different data recovery/partitioning programs (Partition Wizard and PhotoRec/TestDisk
also using "chkdsk" in windows command prompt returns saying that the disk is in the "RAW" format.
Additional info:
Phone: Motorola Droid RAZR HD (XT926) (Verizon)
ROM: XenonHD 11.01 (Android version 4.2.2, AOSP based)
Sorry if this is more lengthy than necessary, just trying to be thorough and cover all the bases!
Thanks in advance for your help!
Hey! I installed the Remix OS beta when it came out at the beginning of this month, and everything worked well. I initially installed it onto an SD as a test, then moved to a USB as I found it to be quite useful, using Resident mode the whole time in order to save files.
I decided to switch USBs I was using, so made a fresh install onto a Integral 32GB USB3 stick. I also installed Phoenix OS onto the same SD I had previously used as a test. I decided to run Phoenix OS first to test it out (it boots fine), then I tired to boot up the new Remix install on the USB. Here's where the problems begin.... Guest mode works 100% (even using a DPI flag at boot), but Resident just hangs. I've tried multiple fresh installs on different USBs and even booting on different PCs. I feel like I'm losing my mind! Any ideas?
Ok, so I'm back to (sort of) answer my own question, just in case anyone else runs into the same problem when attempting to run Resident mode from a USB.
After looking at the boot options I realised that Resident mode was looking to format partition 1 on the USB at boot, this is where the boot was hanging without any confirmation of a successful format. This combined with the fact that Guest mode worked without a hitch made me realised that the partitions on the USB were messed up. I couldn't figure out how to successfully remove all the partitions using windows partition manager, so a quick format using "SD Formatter" (don't stop here as it won't work yet) to remove the partitions and restore the USB to its original size, then a long format using "USB Disk Storage Format Tool" did the trick. It takes about 30mins to format a 32GB USB using these tools, but it's the only method I've found to restore the USB to it's original state.
For future reference, to fix up the disk using built in Windows tools you can just run Diskpart from the command line, then use the following commands:
Code:
list disk
select disk x (whichever the number is for the USB stick)
clean
create partition primary
format fs=ntfs quick
exit
Takes around 1 minute.
This is a working usb install media creator method for remix os installation and legacy bios + MBR format and not GPT and circumventing all known errors made for noobs including USING full drive internal storage space etc.
You will be able to use this usb stick for future creation of other usb install media
you will have the choice to also install to hard drive
you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s
the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.
For first installer drive it will be basic fat 32 install. you will need rufus usb boot media creator
after creation of the installer drive keep it safe i reccommend you use a 4gb drive $4/£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!
Format the second drive with the size of your choice to ext 4 on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)
1. Create fat 32 usb boot disk with first usb drive and rufus usb boot media creator and the remix os iso version 2.0402
2.make sure after creation you boot up the usb drive and enter remix os then shutdown and boot up again to write the config files
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix for version 2.0402 which updates to version 2.0403)(if this update fails you cannot proceed further with instructions unless you have version 2.0403 iso)( this update DOSENT APPLY TO REMIX OS version 2.0403 or 3.0+ INSTALLATION)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself using full drive internal storage space.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: INSTALL=1
9. then press enter then you will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)
**** Newbie Errors to avoid******
1. make sure you format the drive correctly, sometimes errors at this stage will create errors later on and affect later installation and will create boot up failures
2. i have to stress this once again as once i formatted the same drive with the same settings in minitool partition manager but in different order for example: instead of formatting it ext 4 then applying changes then setting it to primary then applying changes then setting the partition to active flag and applying changes, i did format ext 4 and change partition to primary all at once then applied changes then set it to active flag and applied changes and later after remix os install the usb wouldnt boot saying "missing operating system error" so caution.
3. after you format the drive with ext 4 partition the usb drive will be unrecognizable in windows. (do not use windows unplug usb drive feature to remove the drive, just pull it out)
4. make sure you pull the first installer drive out before booting the newly created ext 4 usb as it may affect boot up
5. sometimes for power saving reasons the screen might go blank while installing as installing takes time dont panic just press power button or any key to revive the system
6. if you dont get a usb drive faster than 10 mb/s then you will have problems if you continue with the installation and alot of system lag
7. its happened to me many times before so listen carefully: if you dont format the drive correctly even the drives transfer write speed can be greatly affected for example i formatted the usb drive and made a mistake but it was not detectable as it said all was fine i think i formatted the usb drive fat32 without first deleating the existing partition (just converted it) then with remix os installation at the stage where you boot up the installed drive for the first time to do a drive write speed test it was telling me the drives speed was below 5 mb/s ( the drive was a lexar p23 usb 3.0 16gb 150 mb/s read 60 mb/s write) and warned me about install failure then i formatted the drive again this time deleting the patition first then applying changes and doing the rest of the steps one by one each time applying changes after only changing one setting then at the remix os installation speed test this time it was reporting 60 mb/s write speeds!
8. remix os works like a charm on intel cpus and intel integrated gpus and i dont have other makes to test so this tutorial is only for legacy bios and intel cpu and gpu (tested all working)
9. This is something so basic but having a data indicator led on your usb drive or usb hub will save you waiting hours! most waiting is due to not knowing whats happening or not knowing if there is an error or not so try and get a usb drive with an led that tells you if the system is currently writing/working to disk and when that led stops blinking for a long period e.g 2 mins then you will know the install has crashed or android is not loading. Also with slower drives the waiting period is longer as the system takes longer to write to the drive (a 544MB/s msata SSD FLASH drive takes 5 secs to install while a usb 3.0, 60 MB/s write drive will take 15 mins) but if you have a data status led which shows its still blinking then atleast you will know the installation/loading is still working and no need to abort it. Also Android os constantly writes to the drive when running so you will see the data status led constantly blink too and if that ever stops you know you have encountered a system crash. Also the led shows how well remix os is running as regards speed of the operating system, for example at the start of loading remix os or when doing a task the led stays constanly blinking RAPIDLY but after loading or finishing the task the led defaults to a blink per second (this is classed as normal operation and healthy) but when the led is constantly blinking RAPIDLY without pauses or stays on for a long time then it means the operating system is not running smoothly as it should and then you should check if theres a problem formatting or if its a fake drive etc.
10. Using slow usb drives or fake usb drives will get very HOT and will cause the error "not responding...wait or close" error while very fast drives will always stay COOL without system lag and errors.
note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.
The remix os ota update 2.0403 addresses the boot media creation errors of remix os 2.0402 . After the ota update all drives created with the grub menu installer boot up as they should but only ufi boot up option hangs!
Hope this helps hit the thanks dont forget so i know how many people were helped by this! enjoy.
I have the ativ pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough 5 secs to boot and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all. The 5 year old Ativ pc pro gets 123,000+ score in antutu benchmark same as the latest LG G5 with the latest adreno 530 gpu/snapdragon 820 cpu which costs approx £600 now in retail!!! I bought the Ativ pc pro convertible laptop/tablet for only £200 two weeks ago with accessories (ethernet dock etc) worth alone £100 on its own off ebay!!! On top of all that its also a windows 10 pro convertible laptop/tablet system which on its own without android was initially worth £1200 five years ago and still costing approx £500 even now in retail. So what im trying to say here is that for only £200 i get a £600 android 6.0 laptop/tablet and i also get a £500 windows 10 pro laptop tablet ALL IN ONE. Muahahahahahaha haaaaa hahahaha kekekeke.
http://www.ebay.co.uk/itm/Brand-New...549634?hash=item33bcb8a542:g:UFYAAOSwQItUFG7S ( 128GB Msata SSD 544 MB/s read write )
http://www.ebay.co.uk/itm/231736235624?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT ( USB 3.0 Msata enclosure )
alz_uk said:
This is a working usb install media creator method for remix os installation and legacy bios circumventing all known errors made for noobs including USING full drive internal storage space etc.
You will be able to use this usb stick for future creation of other usb install media
you will have the choice to also install to hard drive
you will need 2 x usb drives and require drive write speed to be higher than 10 mb/s
the first drive will be the installer drive and the second will be the actual usb drive used to run remix os.
For first installer drive it will be basic fat 32 install. you will need rufus usb boot media creator
after creation of the installer drive keep it safe i reccommend you use a 4gb drive $4/£2 off ebay but get something thats got a write speed higher than 10 mb/s or else install will fail!
Format the second drive with the size of your choice to ext 4 on your pc with minitool partition or acronis disk manager (make sure the drive is formatted as primary and set to active flag)
1. Create fat 32 usb boot disk with first usb drive and rufus usb boot media creator and the remix os iso
2.make sure after creation you boot up the usb drive and enter remix os then shutdown and boot up again to write the config files
3.make sure you dont boot up the ufi version of the boot up, only use the legacy version (it will have ufi next to boot drive in bios usb boot up list)
4.after you enter remix os go to settings and download the update (ota) (this is the main fix for version 2.0402 which updates to version 2.0203)(if this update fails you cannot proceed further with instructions unless you have version 2.0403 iso)(DOSENT APPLY TO REMIX OS version 2.0204 or 3.0+ INSTALLATION)
5. After ota update reboot and enter remix os again and let android upgrade
6.after this stage is complete your fat32 remix os usb bootable drive is ready to create a usb drive that runs remix os from the drive itself using full drive internal storage space.
7.insert the second drive in a usb hub and boot up the computer with both drives in the computer and boot from the first drive (the usb remix os installer drive)
8.boot up and at the grub boot menu (it should look blue with yellow writing not the black ufi version) press tab and type: INSTALL=1
9. then press enter then you will enter usb media creation menu select scan usb drives and select the second drive (the remix os running drive)
10. It will ask you what you want to format the drive as so select do not format option (becus you already formatted it)
11.then it will ask you to install first grub boot menu say yes
12. Then it will ask you to install second boot grub efi menu say yes
13. Next it will ask you if you want to format the boot partition or something like that say *** no ***
14. Then it will ask you if you want read/write privelage say yes
15. It will proceed to write the remix os onto the drive
16. When finished it will ask to restart (at this point i just switch the pc off by holding power button then restart and boot off the new second drive to run the os from it already upgraded too)
**** Newbie Errors to avoid******
1. make sure you format the drive correctly, sometimes errors at this stage will create errors later on and affect later installation and will create boot up failures
2. i have to stress this once again as once i formatted the same drive with the same settings in minitool partition manager but in different order for example: instead of formatting it ext 4 then applying changes then setting it to primary then applying changes then setting the partition to active flag and applying changes, i did format ext 4 and change partition to primary all at once then applied changes then set it to active flag and applied changes and later after remix os install the usb wouldnt boot saying "missing operating system error" so caution.
3. after you format the drive with ext 4 partition the usb drive will be unrecognizable in windows. (do not use windows unplug usb drive feature to remove the drive, just pull it out)
4. make sure you pull the first installer drive out before booting the newly created ext 4 usb as it may affect boot up
5. sometimes for power saving reasons the screen might go blank while installing as installing takes time dont panic just press power button or any key to revive the system
6. if you dont get a usb drive faster than 10 mb/s then you will have problems if you continue with the installation and alot of system lag
7. its happened to me many times before so listen carefully: if you dont format the drive correctly even the drives transfer write speed can be greatly affected for example i formatted the usb drive and made a mistake but it was not detectable as it said all was fine i think i formatted the usb drive ext 4 without first deleating the existing partition (just converted it) then with remix os installation at the stage where you boot up the installed drive for the first time to do a drive write speed test it was telling me the drives speed was below 5 mb/s ( the drive was a lexar p23 usb 3.0 16gb 150 mb/s read 60 mb/s write) and warned me about install failure then i formatted the drive again this time deleting the patition first then applying changes and doing the rest of the steps one by one each time applying changes after only changing one setting then at the remix os installation speed test this time it was reporting 60 mb/s write speeds!
8. remix os works like a charm on intel cpus and intel integrated gpus and i dont have other makes to test so this tutorial is only for legacy bios and intel cpu and gpu (tested all working)
9. This is something so basic but having a data indicator led on your usb drive or usb hub will save you waiting hours! most waiting is due to not knowing whats happening or not knowing if there is an error or not so try and get a usb drive with an led that tells you if the system is currently writing/working to disk and when that led stops blinking for a long period e.g 2 mins then you will know the install has crashed or android is not loading. Also with slower drives the waiting period is longer as the system takes longer to write to the drive (a 544MB/s msata SSD FLASH drive takes 5 secs to install while a usb 3.0, 60 MB/s write drive will take 15 mins) but if you have a data status led which shows its still blinking then atleast you will know the installation/loading is still working and no need to abort it. Also Android os constantly writes to the drive when running so you will see the data status led constantly blink too and if that ever stops you know you have encountered a system crash. Also if the the led shows how well remix os is running as regards speed of the operating system, for example at the start of loading remix os or when doing a task the led stays constanly blinking RAPIDLY but after loading or finishing the task the led defaults to a blink per second (this is classed as normal operation and healthy) but when the led is constantly blinking RAPIDLY without pauses or stays on for a long time then it means the operating system is not running smoothly as it should and then you should check if theres a problem formatting or if its a fake drive etc.
10. Using slow usb drives or fake usb drives will get very HOT and will cause the error "not responding...wait or close" error while very fast drives will always stay COOL without system lag and errors.
note: If wanting ntfs version of remix os then its a little complicated than this and you will need to use imgtools to increase the data.img file on the ntfs drive after creation with the first usb media creator drive.
The remix os ota update 2.0403 addresses the boot media creation errors of remix os 2.0203 . After the ota update all drives created with the grub menu installer boot up as they should but only ufi boot up option hangs!
Hope this helps hit the thanks dont forget so i know how many people were helped by this! enjoy.
I have the ativ pc pro xe700t1c the uk version with intel core i5 quad core and its also a convertible tablet with msata ssd as hdd drive and as you all probbaly know android was created for fast flash memory and linux format os so the best combination is an ssd and ext4 linux file format. I have a 64gb 544 mb/s msata drive in a usb 3.0 enclosure which i use to boot remix os and run it off it. Its perfectly smooth and fast enough 5 secs to boot and the ativ pc pro convertible laptop/tablet is fully compatible hadware software wise, no problems at all. The 5 year old Ativ pc pro gets 120,000+ score in antutu benchmark same as the latest LG G5 with the latest adreno 530 gpu/snapdragon 820 cpu which costs approx £600 now in retail!!! I bought the Ativ pc pro convertible laptop/tablet for only £200 two weeks ago with accessories (ethernet dock etc) worth alone £100 on its own off ebay!!! On top of all that its also a windows 10 pro convertible laptop/tablet system which on its own without android was initially worth £1200 five years ago and still costing approx £500 even now in retail. So what im trying to say here is that for only £200 i get a £600 android 6.0 laptop/tablet and i also get a £500 windows 10 pro laptop tablet ALL IN ONE. Muahahahahahaha haaaaa hahahaha kekekeke.
http://www.ebay.co.uk/itm/Brand-New...549634?hash=item33bcb8a542:g:UFYAAOSwQItUFG7S ( 128GB Msata SSD 544 MB/s read write )
http://www.ebay.co.uk/itm/231736235624?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT ( USB 3.0 Msata enclosure )
Click to expand...
Click to collapse
Hey, thanks for the instructions. I managed to use this method to install Remix OS 3.0.102 onto the seconds USB drive on my Macbook Pro. Once the installation process finished I hit Run Android_x86 instead of reboot and it started just fine. The problem is that after I removed the first USB drive with the Remix OS installer and I rebooted the second drive doesn't show up as a boot option. So now I can't get back into it.
Any suggestions?
Thanks,
Daniel
phantasma2983 said:
Hey, thanks for the instructions. I managed to use this method to install Remix OS 3.0.102 onto the seconds USB drive on my Macbook Pro. Once the installation process finished I hit Run Android_x86 instead of reboot and it started just fine. The problem is that after I removed the first USB drive with the Remix OS installer and I rebooted the second drive doesn't show up as a boot option. So now I can't get back into it.
Any suggestions?
Thanks,
Daniel
Click to expand...
Click to collapse
you did the last proccess wrong! you need to follow step 16 properly! It tells you not to run android x86 option or restart option, infact it tells you to switch your pc off then remove the first installer drive then start the pc with the second drive and boot from it. If you run android x86 option at the end it will run but make next boot broken. Please follow instructions carefully.
if you didnt backup your files then you can still boot from it but the boot might not stick unless you reinstall remix os onto the drive again.
do steps 7 to 13 again to the second drive and when you get to step 14 "do you want to write privelage" part just switch the pc off and boot from the second drive again and this time boot should be fixed but might not boot again after that like i said before.
I tried multiple variations and I end up with 2 outcomes (always shut the computer down once the last options was on screen):
1) If I don't tell it to format on step 13 (like in the instructions) I end up not seeing the USB drive as a boot option after restart.
2) If I tell it to format on step 13 I see the USB and I can select it but then I get the Minimal Bash Grub instead of it booting
P.S. I'm doing this with the latest version of Remix OS 3.0.102 on a 2015 Macbook Pro. Have you tested the instructions on a Mac or only a Windows PC?
phantasma2983 said:
I tried multiple variations and I end up with 2 outcomes (always shut the computer down once the last options was on screen):
1) If I don't tell it to format on step 13 (like in the instructions) I end up not seeing the USB drive as a boot option after restart.
2) If I tell it to format on step 13 I see the USB and I can select it but then I get the Minimal Bash Grub instead of it booting
P.S. I'm doing this with the latest version of Remix OS 3.0.102 on a 2015 Macbook Pro. Have you tested the instructions on a Mac or only a Windows PC?
Click to expand...
Click to collapse
All i can say my freind is there are too many numerous variables that can go wrong. all the way from having the correct bios setup and correct boot mode eg legacy or eufi to formatting the drive correctly and using the already complicated and buggered up installer. you just have to trial and error like i did and after a few days i got it all sussed for my pcs (not macs though sorry, not a mac person never was and never will be lol).
the method i have written works 100% for legacy bios and mbr hard disk (not gpt), windows, fast flash drive and for all versions of remix os upto date so far. ive tried it on different flash drives too.
This has to be mentioned , there is alot that jide is doing to prevent users from doing things like what we are doing here now so they are always changing things to make it harder for people to have it their own way! jides way is making money from the masses while our way is a free os! clearly jide will carry on trying to prevent people like us from doing what we want to do such as using full drive internal storage space etc etc. so watch out folks!
Thanks for the answer. I'll just keep trying until I get it to work. There must be way, even if it means learning how to configure grub manually from scratch. It worked just fine on first install until reboot so it has to work somehow.
It would've been nice if Jide provided more info or support on the issue since this is suppose to be a final product. The purpose of free products is to attract attention to other paid products and to their company. That, they have achieved but if said free product is a hacky nightmare full of bugs and lacking documentation it only puts them in a negative light. Then again, in my case this might also be Apple's fault with their closed platform approach and lack of support for certain file systems and standards.
Anyway, have a good night and all the best.
If I manage to get it working I'll be sure to post it here.
i use Unetbootin to install android-x86 or remixos to hdd or usb, easy
Sent from my AOD255 using XDA-Developers mobile app
wizmart said:
i use Unetbootin to install android-x86 or remixos to hdd or usb, easy
Sent from my AOD255 using XDA-Developers mobile app
Click to expand...
Click to collapse
To my understanding the only way to have Remix OS use the entire space of the USB drive is to have it formatted as ext4. Unetbootin cannot use an ext4 formatted drive so yes, I can have it work in multiple ways either using unetbootin or just dd-ing the image to the drive but in both cases I end up with a 4gb storage space in Remix OS. That is why this method seemed like the best one.
hmm..
Yumi also supports android x86 (easyway to make usb stick) and change grub menu
The android installer from XDA hacked version.. seems to create 3 partitions on the USB stick (fat32/ext4/ext4)
-for those how just wish to use a big usbstick.. to run RemixOS (note removing the partitions can not be done with diskmanager from windowz)
any note.. i have on this tuturial... missing: is what if you have nvidia card
then it needs : i915.modeset=0 nouveau.modeset=1 INSTALL=1
Cheers..
phantasma2983 said:
To my understanding the only way to have Remix OS use the entire space of the USB drive is to have it formatted as ext4. Unetbootin cannot use an ext4 formatted drive so yes, I can have it work in multiple ways either using unetbootin or just dd-ing the image to the drive but in both cases I end up with a 4gb storage space in Remix OS. That is why this method seemed like the best one.
Click to expand...
Click to collapse
try and use this windows app to create usb boot disk, it supports uefi bios and legacy bios + 64 bit/32 bit iso and img files. And your right only ext 4 allows full drive internal storage space without modification of any sort out of the box. With NTFS you need to use imgtools to increase the internal storage space.
http://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
unetbootin can use an ext4 if you use it from linux(ubuntu), from windows you install first to hd on reboot inside unetbootin menu you add INSTALL=1 on your entry then choose usb ext4 on drive choice thats how i do
Sent from my AOD255 using XDA-Developers mobile app
Worked great!
Followed your instructions and loaded Remix OS " Remix_OS_for_PC_Android_M_64bit_B2016091202" version: 3.0.205 onto a Sandisk 128GB USB drive with no problems and full access to entire drive. Using the Remix OS installer only gave 64 GB of Data.
Thank you so much for the guide!