Related
Hello guys! I know it's useless, but anyway, we(@MrBIMC and @r3pwn) crafted root-script for Android Wear!
Download and unzip archive, go to the folder with unpacked data and execute the script:
Code:
sh wear-root.sh
*Note that you'll have to re-run this script everytime you reboot emulator*
Enjoy!
MrBIMC said:
Hello guys! I know it's useless, but anyway, we(@MrBIMC and @r3pwn) crafted root-script for Android Wear!
Download and unzip archive, go to the folder with unpacked data and execute the script:
Code:
sh wear-root.sh
*Note that you'll have to re-run this script everytime you reboot emulator*
Enjoy!
Click to expand...
Click to collapse
Can't run that command in CMD, it says : "sh is not recognized as internal command" on windows
Ashutos1997 said:
Can't run that command in CMD, it says : "sh is not recognized as internal command" on windows
Click to expand...
Click to collapse
For Windows, you'll need to double-click on the .bat file.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
For Windows, you'll need to double-click on the .bat file.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Can u give me proper steps to root ?
Update : ROOTED
Q
@MrBIMC
why should i root it?
is there any app for it to need root access?
or any feature we can access after root?
:good:
I can only imagine what kind of apps Developers will make for rooted smartwatches. We will have to wait and see what wear offers without them first...
x102x96x said:
@MrBIMC
why should i root it?
is there any app for it to need root access?
or any feature we can access after root?
:good:
Click to expand...
Click to collapse
Actually, we don't need to root smartwatch, at least yet. I made a script just because I can, lol
MrBIMC said:
Actually, we don't need to root smartwatch, at least yet. I made a script just because I can, lol
Click to expand...
Click to collapse
absolutely good reason
No need YET.
x102x96x said:
absolutely good reason
Click to expand...
Click to collapse
I'm with you. Although there may not be much of a need at the time I can see this come in handy when I go and pick up a Wear device and start tinkering. I can already think of a few uses for it. And you know what? Even if I fail, it's future proofing. Who knows what the future may bring with Wear devices and their restrictions/Wear skins?
Can i use it on my galaxy young bro?
i
Slick101 said:
Can i use it on my galaxy young bro?
Click to expand...
Click to collapse
use what on Galaxy young?
it s not root method for mobile device. it s for AndroidWear emulator
u should use eclipse to install androidWear SDK and then create AVD of it
see this thread to understand more;
http://forum.xda-developers.com/android-wear/development/app-androidwear-t2690062
:good:
thanks, but this release will run successful on windows+x86 avd
busybox.net/downloads/binaries/latest/busybox-i686
After a long time of trying to get things right, i finally got things right.
So here it is:
TWRP RECOVERY 3.2.1-0 FOR THE MOTO X FORCE (KINZIE)
This is an actual port and not a recompile of a different version for another device.
It is not yet official but i intend to submit my device tree, so it gets official.
It is probably never going to be official, but i'll try and provide frequent updates.
Everything *should* work, as far as i was able to test.
I am not sure about encryption though, as i have not encrypted my device, nor do i intend to do so atm.
Encryption should be ok now. (TWRP team has put a lot of effort in this).
Encrypted partitions cannot be read atm.
This would probably also work for the Droid 2 Turbo, if someone finds a way to unlock the BL.
I will try to maintain TWRP for this device, fixes may take a while though as i am not having a lot of time to work on this.
Installation:
1. Unlock your device
2. Download the image
3. Power off the phone
4. Boot to fastboot (VOL DN + POWER)
5. plug your usb cable install via fastboot:
Code:
fastboot flash recovery TWRP_3.2.1-0_Kinzie.img
If you want to keep OTA Update ability you can also temporary boot to TWRP. You would have to repeat this step everytime you want to go to TWRP then:
Code:
fastboot boot TWRP_3.2.1-0_Kinzie.img
Download here:
Version 3.2.1-0
http://www.mediafire.com/file/o6gcj4hhjahf936/TWRP_3.2.1-0_Kinzie.img
Version 3.1.1-0
http://www.mediafire.com/file/y2k08c6m5tazhbo/TWRP_3.1.1-0_Kinzie.img
Version 3.1.0-0
https://www.mediafire.com/?7h4u37ddiohwy45
Credits go out to the people of Teamwin Recovery project for creating this nice piece of software!
And credits go to @Arasthel, who is a great dev!
Official Changelog 3.2.1-0
Fixes for kinzie:
- USB OTG now working
- TWRP internal folder should be now accessible via /sdcard symlink
- cm updater is reporting device correctly now as kinzie
Amazing, the most beautiful and wanted TWRP version! Tested and working perfectly! Using it as my recovery, not boot only.
Enviado de meu XT1580 usando Tapatalk
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Arasthel said:
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Click to expand...
Click to collapse
To be honest, differences are marginal at this point, as of now we've got the fstabs by-name assignments there is almost no way of messing things up with partition assignments (which is kinda the no. 1 thing to do right in recovery). At the moment i am still using a prebuilt kernel and ramdisk i extracted from the device, because when i started building the device tree the kernel sources haven't been available. And when they finally were i decided to first fix the issues i already had, before introducing new ones. The whole graphics sub routines of TWRP (minuitwrp) recently had undergone a pretty big overhaul and so we've lost ability to flip screen on the way. I recently made a patch to fix this for overlay devices (which the kinzie is), and since then, TWRP is running fine on the native kinzie build. The overhaul also made the use of a custom graphics.c obsolete. (I suspect you had to use that?) I made the device tree mostly from scratch, only looking at similiarities at trees from hima and clark. (Hima has msm8994 too, clark has a different chipset as you know, but is a moto device).
You can have a look at it here. Please note that this is not absolute latest configuration (haven't uploaded it yet) and it still needs a little cleanup before submission. After that, i am going to throw in kernel sources from motorola and fetch the prebuilts necessary.
If you are interested in learning more you can contact me via PM.
Just flashed and working 100%. Moto X force BR version.
Thx a lot dude :good: just flashed and working.
no more upside/down issue :silly:
and nice theme btw
Thanks a lot mate! working as expected.
Perfect and beauty one! Thanks!
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
marzliak said:
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
Click to expand...
Click to collapse
I'll look into it as soon as I can. Might also be a general issue in twrp.
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Moderator Edit: @MuyKurioso - it is not necessary or desirable to quote the entire OP. Some users have limited bandwidth or are Mobile - this can affect page load times. Please consider this in the future. Thanks.
Are you currently trying to port CM to Kinzie? Or just waiting to help out someone? Just curious, and thanks for all your hard work in this recovery!
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Does this work for the turbo 2?
Xadro said:
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Click to expand...
Click to collapse
I have backed up to the internal emulated sdcard.
I wanted to sync the folder and backup to my NAS
Sent from my XT1580 using Tapatalk
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
AztekSoul said:
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Click to expand...
Click to collapse
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Sent from my XT1580 using Tapatalk
fubofo said:
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Click to expand...
Click to collapse
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Xadro said:
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Click to expand...
Click to collapse
Thanks, managed to chown the directory in terminal emulator. All works great now, thanks
Sent from my XT1580 using Tapatalk
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
rodrigoger said:
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
Click to expand...
Click to collapse
There is something for you in the OP
Hi, is the remix os for pc 2.0.202 release out? there's a release note on http://support.jide.com/hc/en-us website. but OTA update doesn't say so and download page isn't updated either.
Enable test builds in settings.
Its not out yet, probably getting it ready for release soon i hope, and hopefully we have audio this time around!
enable latest update in setting/about page and tap 5 time "Remix OS version" to show aditional update call "unstable update"(well its stable enough for me"
and the new update has new feauture, it has pre-rooted native apps in it ( no need to install superuser or any other root apps anymore)
just do install remix os beta update to latest 2.0.202 and replace init.img file with one that have R/W in system, cause original init.img file still only has R/O system
note : backup ur original init file for next update, cause OTA update without original init file will fail..
Ok, I was able to download the update this morning! Not sure what was added or fixed but i was sad to see audio is still not working
this remix os never worked on my computer, the installation never finish successfully . I wonder if it's a matter of driver, like my asus essence stx sound card.
Go to Setting then "About" and tap "Remix OS version" 5 times to show (unstable update). Then go back to Settings click on "Update", click on the 3 little dots (options), click "System update version options", then select "Unstable version", and go back to "Update" and it will be there.
I downloaded and placed the initrd.img into the Remix OS folder, but when any app asks for root it fails with message "libc.so is 32 bit"
Anyone know what's going on? I installed 64 bit version.
lollyjay said:
I downloaded and placed the initrd.img into the Remix OS folder, but when any app asks for root it fails with message "libc.so is 32 bit"
Anyone know what's going on? I installed 64 bit version.
Click to expand...
Click to collapse
Yep.
Orion116 said:
Yep.
Click to expand...
Click to collapse
Oh thanks for your support
Sent from my on Z00A using XDA Labs
https://groups.google.com/forum/m/#!topic/tasker/y7a-SBGEyJI
I think we need something like this.
lollyjay said:
Oh thanks for your support
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
Try use 32 bit, I am using 32 bit and root is works
arts821 said:
Try use 32 bit, I am using 32 bit and root is works
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 7 using XDA Labs
arts821 said:
enable latest update in setting/about page and tap 5 time "Remix OS version" to show aditional update call "unstable update"(well its stable enough for me"
and the new update has new feature, it has pre-rooted native apps in it ( no need to install superuser or any other root apps anymore)
just do install remix os beta update to latest 2.0.202 and replace init.img file with one that have R/W in system, cause original init.img file still only has R/O system
note : backup ur original init file for next update, cause OTA update without original init file will fail..
Click to expand...
Click to collapse
My init.img file was by default R/W... Tried a few apps that said i do not have root access and or missing superuser... Downloaded a build.prop editor to fix opengl settings and they wont stick...
Any help would be appreciated, im trying to get gameloft games to stop force closing on startup per https://groups.google.com/forum/#!topic/remix-os-for-pc/-UZXopMPj6o
*note my opengl settings were by default already set to "131072" but this is not working for gameloft games.
jzen said:
My init.img file was by default R/W... Tried a few apps that said i do not have root access and or missing superuser... Downloaded a build.prop editor to fix opengl settings and they wont stick...
Any help would be appreciated, im trying to get gameloft games to stop force closing on startup per https://groups.google.com/forum/#!topic/remix-os-for-pc/-UZXopMPj6o
*note my opengl settings were by default already set to "131072" but this is not working for gameloft games.
Click to expand...
Click to collapse
What actually opengl es version is supported by ur GPU driver in remix os , u can find it in setting/about page at the bottom, try change the value with proper version reported
Code:
http://www.ltr-data.se/opencode.html/#ImDisk
You can use that to mount system.img or data.img under windows to a virtual drive
arts821 said:
enable latest update in setting/about page and tap 5 time "Remix OS version" to show aditional update call "unstable update"(well its stable enough for me"
and the new update has new feauture, it has pre-rooted native apps in it ( no need to install superuser or any other root apps anymore)
just do install remix os beta update to latest 2.0.202 and replace init.img file with one that have R/W in system, cause original init.img file still only has R/O system
note : backup ur original init file for next update, cause OTA update without original init file will fail..
Click to expand...
Click to collapse
The 202 update shows in the update box as being downloaded. I am then given the option to reboot and install, but when I do, nothing changes. Does my installation have to be rooted first? I have Remix installed on the hard drive (SSD) of my Acer Timeline 1810TZ.
trentfox said:
The 202 update shows in the update box as being downloaded. I am then given the option to reboot and install, but when I do, nothing changes. Does my installation have to be rooted first? I have Remix installed on the hard drive (SSD) of my Acer Timeline 1810TZ.
Click to expand...
Click to collapse
I have a similar problem. I'm running 2.0.102 as the only OS on an Acer touch-screen laptop that is booting from a 64GB SSD. Everything is working fine.
However, the Update window shows that Remix OS 2.0.202 B2016040501 has been downloaded.
When I click the "Reboot and Install button", the machine verifies the OTA package and reboots.
Problem is: the OS hasn't been updated at all and I'm still in 2.0.102, even though "Options / Automatically install updates" is turned on.
A step-by-step guide on how to fix this would be greatly appreciated.
FOUND: An accurate and detailed guide is here:
http://forum.xda-developers.com/remix/remix-os/remix-os-hard-drive-virtual-machine-t3362506
Q8-V08 said:
Code:
http://www.ltr-data.se/opencode.html/#ImDisk
You can use that to mount system.img or data.img under windows to a virtual drive
Click to expand...
Click to collapse
how to use it??
kretex said:
how to use it??
Click to expand...
Click to collapse
Right click your .Img file, ImDisk creates a shortcut for mounting.
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Regnas said:
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Click to expand...
Click to collapse
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Dude...just try and will know the answers [emoji4]
bombaglad said:
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Click to expand...
Click to collapse
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
kretex said:
Dude...just try and will know the answers [emoji4]
Click to expand...
Click to collapse
I'm triple boot Win 10, win7 and Phoenix OS, so I'm a little afraid of mess things up.. It would be a nightmare.......
Regnas said:
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
Click to expand...
Click to collapse
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
putr4s said:
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
Click to expand...
Click to collapse
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
putr4s said:
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Click to expand...
Click to collapse
Thanks for the support.
Fortunately (I hope) I'm on BIOS as well, cause I heard somewhere that disabling secure boot prevents Windows to boot. I don't know if it's a Windows requirement on UEFI machines...
Now it's time to build courage to install it....
Cheers..
bombaglad said:
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
Click to expand...
Click to collapse
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
putr4s said:
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
Click to expand...
Click to collapse
Interesting method...
Thanks for sharing..
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
no need to expand at all, you can choose between 8, 16 and 32GB
bombaglad said:
no need to expand at all, you can choose between 8, 16 and 32GB
Click to expand...
Click to collapse
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Regnas said:
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Click to expand...
Click to collapse
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
bombaglad said:
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
Click to expand...
Click to collapse
Thank you Sir.
Cheers.
So.....the problem solved [emoji16]
kretex said:
So.....the problem solved [emoji16]
Click to expand...
Click to collapse
We're getting there........
Finally I installed it on my Hard Drive... Everything seems to be working fine...
Thank you guys for all the info, help, support and whatnot...
Cheers..
Hi,
I have been using Remix OS for weeks now. It is an amazing operating system. I have tried Linux and Mac as an alternative for Windows, and only Remix OS made me use use it as my main OS. I would keep it as my main OS but I have this major annoyance with the latest version. For some reason, I could not access my secondary hard drive. This sucks because that's were I keep all my files and downloads. If someone could please post a working guide on how to enable it, I would be very thankful.
Thank you.
I'm currently using StickMount & works perfect, except for one thing... SD Maid: I don't know to do to the System Cleaner section not recognize the other partitions... tried adding them to the exclusions but does'nt work, I can only unmount then remount.
xSilverLight said:
I'm currently using StickMount & works perfect, except for one thing... SD Maid: I don't know to do to the System Cleaner section not recognize the other partitions... tried adding them to the exclusions but does'nt work, I can only unmount then remount.
Click to expand...
Click to collapse
What are you excluding? /sdcard/usbStorage/ or /data/media/0/usbStorage/
HypoTurtle said:
What are you excluding? /sdcard/usbStorage/ or /data/media/0/usbStorage/
Click to expand...
Click to collapse
I Tried several routes except /data/media/0/usbStorage/... i'll try with that and tell you later thanks :silly:
xSilverLight said:
I'm currently using StickMount & works perfect, except for one thing... SD Maid: I don't know to do to the System Cleaner section not recognize the other partitions... tried adding them to the exclusions but does'nt work, I can only unmount then remount.
Click to expand...
Click to collapse
Thank you. I will give it a try and I will post the results. I am currently running 403 64-bit. I'll play around with StickMount first before I reinstall 3.0
xSilverLight said:
I Tried several routes except /data/media/0/usbStorage/... i'll try with that and tell you later thanks :silly:
Click to expand...
Click to collapse
Some apps can be a bit odd when using root (and not follow symlinks); /sdcard should be a symlink to /data/media/0 so that might work here...
Digong said:
Thank you. I will give it a try and I will post the results. I am currently running 403 64-bit. I'll play around with StickMount first before I reinstall 3.0
Click to expand...
Click to collapse
Hope it work for you, good luck
HypoTurtle said:
Some apps can be a bit odd when using root (and not follow symlinks); /sdcard should be a symlink to /data/media/0 so that might work here...
Click to expand...
Click to collapse
Yes xD, hope it works, I'll try in a while.. I'm still in Windows :fingers-crossed:
Digong said:
Hi,
I have been using Remix OS for weeks now. It is an amazing operating system. I have tried Linux and Mac as an alternative for Windows, and only Remix OS made me use use it as my main OS. I would keep it as my main OS but I have this major annoyance with the latest version. For some reason, I could not access my secondary hard drive. This sucks because that's were I keep all my files and downloads. If someone could please post a working guide on how to enable it, I would be very thankful.
Thank you.
Click to expand...
Click to collapse
First follow directions here: http://forum.xda-developers.com/remix/remix-os/guide-modify-remix-3-0-101-t3428553
Next install SuperSU from Play Store
Next install StickMount from Play Store
In StickMount mount mass storage devices
You will find your drives in folder called usbStorage
Sent from my on Z00A using XDA Labs
lollyjay said:
First follow directions here: http://forum.xda-developers.com/remix/remix-os/guide-modify-remix-3-0-101-t3428553
Next install SuperSU from Play Store
Next install StickMount from Play Store
In StickMount mount mass storage devices
You will find your drives in folder called usbStorage
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
lollyjay,
i tried to follow the command and i got an error:
i am sure about the path, cause i have always converted RemixOS to NTFS without issues.
Please advise.
Digong said:
lollyjay,
i tried to follow the command and i got an error:
i am sure about the path, cause i have always converted RemixOS to NTFS without issues.
Please advise.
Click to expand...
Click to collapse
Ignore my posted screenshot above. I got it resolved by moving the RMXTools folder to the desktop instead of my secondary hard drive.
@lollyjay, xSilverlight thanks for your help guys. It worked. I am using Solid Explorer as my File Manager and although it is no longer showing by default, I can always add it to bookmark for easy access.
Digong said:
Ignore my posted screenshot above. I got it resolved by moving the RMXTools folder to the desktop instead of my secondary hard drive.
@lollyjay, xSilverlight thanks for your help guys. It worked. I am using Solid Explorer as my File Manager and although it is no longer showing by default, I can always add it to bookmark for easy access.
Click to expand...
Click to collapse
Very glad to see you solved it
lollyjay said:
Very glad to see you solved it
Click to expand...
Click to collapse
thanks again. however, i ended up rolling back to 403 64bit. 3.0 seems slow and laggy in my system. 8ball pool crashes too :/ will wait for a better update.
edit fstab.remix_x86，fstab.remix_x86_64，https://source.android.com/devices/storage/config.html
cd /sys/dev/block ，ls -al，cd /sys/block
example fstab
none /cache tmpfs nosuid,nodev,noatime defaults
/devices/*/usb*/* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/platform/*/mmc* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/*/* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
I don't HDD should /device/platform/……，you can cd /sys/block，ls -al