If any of you have install Remix OS as a dual boot or in the internal storage then Remix OS can be updated with ease. Please don't delete your data.img file during this process.
1. Copy the new *.iso files in the package and overwrite the older one.
2. Generate the bootable usb drive drive with included usb tool and copy all the content from the usb to your Remix drive. Overwrite files if necessary.
3. Reboot your pc/laptop/tablet to remix os. It will take some time to update.
4. Voila! Remix os has been updated with battery icon and other small fixes.
What about pre-rooted system.img ? I use a rooted remix os and if I use this method, will it affect the system.img?
TheBasterd said:
What about pre-rooted system.img ? I use a rooted remix os and if I use this method, will it affect the system.img?
Click to expand...
Click to collapse
will require manual re-rooting....by whichever method you acquired?
but...who has a copy of the updated iso?
Related
I have an 8gb nook tablet that I rooted probably 2 and a half years ago and haven't changed anything on it since. I am wanting to undo and update to current root and flash a 4.4 rom like on my phone. What is the best way to go about this? I know how to unroot, I just need to know the best way to root currently. Thanks.
Custom ROMs like CM comes with built-in root capability, and moreover once installed replaces completely the existing ROM currently in place (be it stock ROM, rooted stock ROM, or another custom ROM). As such, there is no need to root (or re-root) prior to flashing a custom ROM. See http://forum.xda-developers.com/showthread.php?t=2575489 for more background info and pointers.
Cool, thanks for the reply and links. I have some reading to do.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also? Will it work for CM11 also?
ryknow27 said:
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also?
Click to expand...
Click to collapse
Yes.
Will it work for CM11 also?
Click to expand...
Click to collapse
It should work (with the usual caveat YMMV). Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later (in step 2(b) of http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123); you can find the SD version of TWRP 2.6.3.x at http://techerrata.com/browse/twrp2/acclaim. You also need a recent Gapps version corresponding to the CM11.
Alternatively, if your NT is already on CM10.x (as my NT was), you can:
download CM11 ROM and the corresponding Gapps zip files onto your NT (user content media partition).
use SD based recovery to flash a flashable emmc CWM zip (http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2) or flashable emmc TWRP zip (http://forum.xda-developers.com/showpost.php?p=49111924&postcount=8) into emmc.
remove SD then boot onto emmc recovery (which is installed in step 2) and use it to install the ROM and Gapps zip files downloaded in step 1.
Remember to use SD based recovery to backup your current ROM before flashing CM.
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
ryknow27 said:
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
Click to expand...
Click to collapse
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
digixmax said:
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
Click to expand...
Click to collapse
I did try 7-zip first and it didn't work. I may have just done something wrong. I'll try it again. Thanks for all the help.
I moved a pre-rooted system.sfs to my remix drive and tried to run SuperSU but when i try to update the binary it always fails. Any idea why? I can provide whatever info is needed
fix error update binary superSU
Note: change system.sfs to system.img, don't use system.sfs
tuong1008 said:
Note: change system.sfs to system.img, don't use system.sfs
Click to expand...
Click to collapse
how? do i rename the file? reinstall the os?
Quote100 said:
how? do i rename the file? reinstall the os?
Click to expand...
Click to collapse
RMXtools [emoji4]
original Thread Here : http://forum.xda-developers.com/remi...a-img-t3308158
Remix OS Root Method with windows For 2.0 or Below Version
Video Tutorial : https://www.youtube.com/watch?v=JV6vZqGQ4sE
For Downloading RMX Tool v1.5 Download Here : Owner Link | External Link
Remix OS Root Method with windows For 2.0.101 and Above Version
Video tutorial : https://www.youtube.com/watch?v=IFGzmc81ta0
Ref :http://forum.xda-developers.com/remix/remix-os/how-to-root-remix-os-windows-video-t3311406
Thanks to kabeerkhan2016 for Video, and imadlatch for RMX Tool
my remix os is system.img but still same can't update binary su, remix os 64 bit new version.. i using rmx tool 1.7 fix version
Su Binary Installation Failed !!
I have installed RemixOS 3.0.207 64bit and rooted using RMXtools 1.8 Fix. But SuperSu shows Su Binary needs updated. When I click update, installation fails. I have tried converting system.sfs into system.img it gets same error. Help Me !!
The latest update of the Remix OS 2.0.202 now has pre-rooted feature. no need to install the super user or any other root apps, simply by changing the file init.img with the one that has a R/W system and we are now rooted( cause the original init.img from jide still has R/O system in it), nice feature Jide and TY for great OS
oh ya, for who is not having this update, it is in unstable version. tap 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS ( stable enough for me)
note: keep and backup the original files init.img as will be needed for OTA update
because if the original file is missing or replaced OTA update will fail..
enjoy it..
Cannot find init.img file that has a R/W system
This is really cool and I have just updated my Remix OS installation with the latest update (2.0.202) but I don't know where to find the init.img file that has a R/W system in order to have root access. Thanks for your help...
stathious said:
This is really cool and I have just updated my Remix OS installation with the latest update (2.0.202) but I don't know where to find the init.img file that has a R/W system in order to have root access. Thanks for your help...
Click to expand...
Click to collapse
u can download init file that has R/W system 32 bit or 64 bit , here
can you share the download link with files of 2.0.202 version, because when i click reboot and install button it goes straight to Windows and does nothing !?
Thanks in advance
Where i put the initrd.img on my remix os drive ? Prerooted features means that I can install application that needs root or not ?
tasadar said:
can you share the download link with files of 2.0.202 version, because when i click reboot and install button it goes straight to Windows and does nothing !?
Thanks in advance
Click to expand...
Click to collapse
use stock beta version Remix OS u can download update 2.0.202 only from stock unmodified rom
Almercer said:
Where i put the initrd.img on my remix os drive ? Prerooted features means that I can install application that needs root or not ?
Click to expand...
Click to collapse
put init file in where u install remix os in RemixOS folder, yes pre-rooted means it already rooted from the 1st u update remix to version 2.0.202, and if u want u can update root feature with superSU directly from Remix after booting from playstore,
I am not getting root even after adding the intrd.img. Yes, I am using 2.0.202.
Root behaviour is same as previous build for me i.e. Alt&F1 has root; system doesn't.
@arts821 any chance you are using 32bit?
I have root anyway; using my system-less root ramdisk.img; just curious on how the stock su via settings works...
Also changing to a rw initrd shouldn't be needed for root to work as in OP, but is needed to alter ant system files; but note mounting system as rw will break OTA and require restoring an unaltered version.
No root access with this
Hmm..maybe not all system have this feature, try install supersu from play store to make sure as u can see in my screenshot the root feature icon is setting icon, and yes I using 32bit remix, and wipe all my data.img(fresh install)
It seems only 32bit is rooted, which sucks because I like using all my RAM, I have 8gb ram, lol.
I could not install the .202 although I am using stock version. After click reboot and install it just reboots to old version. Please give download link with sysmtem file of the new version !?
Ps: I am using it on z3740 cpu tablet
can someone upload version 2.0.202? cause my laptop processor won't boot any previous version and this version provides a special fix for it. Compress system from img to sfs using RMXTools, kernel and initrd files and archive them, I will replace them in my iso.
Thanks in advance..
I guess it's not possible do to change the file in Remix Mini since root would be need to change that file...isn't it?
arts821 said:
u can download init file that has R/W system 32 bit or 64 bit , here
Click to expand...
Click to collapse
dumb question, will placing that file in a 2.0.102 build give root?
dkryder said:
dumb question, will placing that file in a 2.0.102 build give root?
Click to expand...
Click to collapse
Yes, and no. If you are on 32bit your good to go but 64bit is a no go.
HypoTurtle said:
Root behaviour is same as previous build for me i.e. Alt&F1 has root; system doesn't.
@arts821 any chance you are using 32bit?
I have root anyway; using my system-less root ramdisk.img; just curious on how the stock su via settings works...
Also changing to a rw initrd shouldn't be needed for root to work as in OP, but is needed to alter ant system files; but note mounting system as rw will break OTA and require restoring an unaltered version.
Click to expand...
Click to collapse
Would you mind sharing a link to your ramdisk.IMG? Please??
electrikjesus said:
Would you mind sharing a link to your ramdisk.IMG? Please??
Click to expand...
Click to collapse
Are you on 64 or 32bit?
I have 64bit remix and 32bit phoenix done; will need a copy of 32bit Remix to do one for that (the phoenix one might work as is)
64 is at the top here
i'm on 32bit, replaced initrd.img, installed super su, but no root for me, i tap 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS but no root after reboot
EDIT: FIXED i'm on dual boot, entered from windows, deleted data.img and system. img, copied again system.img from remixos iso, tapped 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS, tested in terminal su command and now it's all ok!
dear i need help
due to many reasons i installed remix os on ext4 partition scheme without data.img and placed boot efi to other partition and everything is fine except now when i am going to update to 3.203 from 3.202, at restart em gotting "update failed" at boot.
plz help
http://forum.xda-developers.com/showpost.php?p=66455430&postcount=7
Ota updating has not being fixed (did it? Ever work?)
*when you download the iso... there a known issues list...that incl Ota not working
Goodluck
mitchell4you said:
http://forum.xda-developers.com/showpost.php?p=66455430&postcount=7
Ota updating has not being fixed (did it? Ever work?)
*when you download the iso... there a known issues list...that incl Ota not working
Goodluck
Click to expand...
Click to collapse
OTA updates of installed RemixOS versions never worked. But you can perform a new installation keeping your data directory. Updating version 3.0.202 you have to rename directory "android-2016-08-23" into "RemixOS" (probably this renaming of the installation directory is necessary the last time) and to delete all directories and files contained by "RemixOS" other than "data". In the next step you have to install Remix OS 3.0.203 without formatting your ext4 partition and with creating a new grub entry. That's all.
remixtester said:
OTA updates of installed RemixOS versions never worked. But you can perform a new installation keeping your data directory. Updating version 3.0.202 you have to rename directory "android-2016-08-23" into "RemixOS" (probably this renaming of the installation directory is necessary the last time) and to delete all directories and files contained by "RemixOS" other than "data". In the next step you have to install Remix OS 3.0.203 without formatting your ext4 partition and with creating a new grub entry. That's all.
Click to expand...
Click to collapse
I've used the ota updater and it worked fine. i didn't test 2.0 to 3.0 ota(it was faster downloading separate and manually update). I have been using the same /remix/data folder since the 2.0(I manually patched /data when going from 2.0 to 3.0). I also keep backups of the data folder.
Maromi said:
I've used the ota updater and it worked fine. i didn't test 2.0 to 3.0 ota(it was faster downloading separate and manually update). I have been using the same /remix/data folder since the 2.0(I manually patched /data when going from 2.0 to 3.0). I also keep backups of the data folder.
Click to expand...
Click to collapse
remixtester said:
OTA updates of installed RemixOS versions never worked. But you can perform a new installation keeping your data directory. Updating version 3.0.202 you have to rename directory "android-2016-08-23" into "RemixOS" (probably this renaming of the installation directory is necessary the last time) and to delete all directories and files contained by "RemixOS" other than "data". In the next step you have to install Remix OS 3.0.203 without formatting your ext4 partition and with creating a new grub entry. That's all.
Click to expand...
Click to collapse
i know the directry is "android-2016-08-23". how i rename it ? i cannot read ext4 from os x not intrested to install fuse.etc
remixtester said:
OTA updates of installed RemixOS versions never worked. But you can perform a new installation keeping your data directory. Updating version 3.0.202 you have to rename directory "android-2016-08-23" into "RemixOS" (probably this renaming of the installation directory is necessary the last time) and to delete all directories and files contained by "RemixOS" other than "data". In the next step you have to install Remix OS 3.0.203 without formatting your ext4 partition and with creating a new grub entry. That's all.
Click to expand...
Click to collapse
Maromi said:
I've used the ota updater and it worked fine. i didn't test 2.0 to 3.0 ota(it was faster downloading separate and manually update). I have been using the same /remix/data folder since the 2.0(I manually patched /data when going from 2.0 to 3.0). I also keep backups of the data folder.
Click to expand...
Click to collapse
There never was a 2.0 to 3.0 ota afaik. The data would have caused a system stall if there was - as it [X86update] isn't setup to clear the system app app-data.
ext4 data shouldn't have any bearing on OTAs and neither should the name of the folder being used [as long as it is correctly labelled in grub as SRC=${folder_name}. ext4 system would be a problem [but as long as there is also a system.sfs in the $SRC folder - that you'll use to remake the system folder - you'll be fine]
Only real issue is if you have grub at a non-standard location [i.e. not sda1/efi] but they have added the grub arg. REMIXOS_EFI=/dev/sda1 or something that you can use to get around that - or just manually fixing the grub.cfg with whatever the OTA is attempting to change it to.
karamatks said:
i know the directry is "android-2016-08-23". how i rename it ? i cannot read ext4 from os x not intrested to install fuse.etc
Click to expand...
Click to collapse
You have to start your computer using a pendrive containing an operating system which can mount your RemixOS partition. Examples are a pendrive containg Ubuntu or PartedMagic. Directory android-2016-08-23 has to be renamed into RemixOS. After opening the renamed directory RemixOS don't forget to delete all files and directories other than "data".
remixtester said:
You have to start your computer using a pendrive containing an operating system which can mount your RemixOS partition. Examples are a pendrive containg Ubuntu or PartedMagic. Directory android-2016-08-23 has to be renamed into RemixOS. After opening the renamed directory RemixOS don't forget to delete all files and directories other than "data".
Click to expand...
Click to collapse
I've got a dual boot tablet that can run Android 5.1 and Windows 10. Both systems are available for download as .RAR files for flashing directly to the device.
I was wondering if there would be a way to convert the flashable Android ROM files to an ISO for installing onto a USB/Micro SD card, much like an Android x86 USB installation?
Alternatively, would it be possible to extract device drivers from the OEM Flashable ROM and add those to an Android x86 ISO?