Thanks to HypoTurtle for providing the .img files! I used them for this, and please give him thanks too. Here is the link to his post: http://forum.xda-developers.com/remix/remix-os/systemless-root-remixos-64bit-t3368131
Looking for a step-by-step to root the most recent .205 Remix OS? I have tried here to put together a procedure that most can follow. Please let me know how it works for you.
PLEASE REMEMBER THAT MESSING AROUND MIGHT RESULT IN PROBLEMS IF YOU DO NOT FOLLOW INSTRUCTIONS EXACTLY.
This is only for 64 bit. Please note that you MUST type all command line commands Exactly as shown (including spaces and caps)
First, download and install Remix OS from their website. Go through the complete installation.
Next, using the Remix Browser, download the following four files:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkVWRxU3pYMzVUWEU
To substitute the new ramdisk.img:
Open the File Manager twice from the file launcher. You should now have two windows open. You can move them around and resize as needed.
From one File Manager window, click on the Drive# with your Remix OS folder (Usually it it the bottom drive on the lower left). You will see a Remix OS folder.
Click on it to open it. Now you should see the files including one named ramdisk.img.
Click on the ramdisk.img and select Rename from the upper right menu (you should see a check symbol... click on this and then click on the three dots to bring up the Rename command). Rename the ramdisk.img to ramdiskorig.img (this will save it in case you want to accept OTA (just rename ramdisk.img to ramdiskroot.img and rename ramdiskorig.img to ramdisk.img))
Tap on the Download Folder of the other File Manager window to open it. You should see the four files you downloaded.
Drag ramdisk.img from Download Folder on the first File Manager window to the Remix OS folder in the other window. You have now replaced the original ramdisk with the "rooted" one.
Now you need to transfer the su.img file into the /data partition:
Press Alt-F1 to open the command line. You should see a line of text with the # symbol.
To copy su.imginto /data, at the command line type: cp /data/media/0/Download/su.img /data/su.img and press ENTER. Note the locations of the spaces after cp and img. If you receive no error statement then you did it correctly.
While you are here, you can activate Google Play store:
type sh /data/media/0/Download/Playenable.sh and press ENTER. You should get an acknowledgement that files are being disabled and enabled.
Press Alt-F7 to exit the command line
Reboot your computer again into Remix OS. You should be rooted, and have Play Store if you did everything correctly. Don't be concerned if you have a little trouble getting Play Store to work at first. Just be patient and keep trying. You may need to go to Setup/Accounts and delete and reenter your Google account.
Many users want to have a different launcher from the one in Remix OS. If you wish to use your launcher of choice:
Download your launcher from Play store
Press Alt-F1 to open the command line
Type sh /data/media/0/Download/Launcherenable.sh and press ENTER. You should see an acknowledgement if you did this correctly.
Now follow these steps to activate the new launcher:
Press Alt-F1 to exit the command line.
You will be prompted to select your launcher. You will have to minimize the launcher (in upper right corner) in order to click the prompt. After enabling your launcher, be sure to go to the Settings/Applications and set your launcher to Open in full screen mode.
Set to go! Have fun.
Where is the ramdisk.img?
64bit or 32bit
thanx
c0dex said:
Where is the ramdisk.img?
Click to expand...
Click to collapse
You should see 4 files. Are they there?
Sent from my on Z00A using XDA Labs
deaakl said:
64bit or 32bit
thanx
Click to expand...
Click to collapse
Thanks for the question. 64 bit. I'll update the OP.
Sent from my on Z00A using XDA Labs
lollyjay said:
Thanks for the question. 64 bit. I'll update the OP.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
worked and solve my problem with usb host controller : (sh: [2]: /data/data/hu.sztupy.android.usbhostcontroller/files/your_binary: permission denied)
thanx
deaakl said:
worked and solve my problem with usb host controller : (sh: [2]: /data/data/hu.sztupy.android.usbhostcontroller/files/your_binary: permission denied)
thanx
Click to expand...
Click to collapse
Good to hear.
hi I just modified the op to make the root process easier.
Sent from my LENOVO 33476WU using XDA Labs
Hi, with this root method, cannot edit init.sh?
RoboR1 said:
Hi, with this root method, cannot edit init.sh?
Click to expand...
Click to collapse
Not directly without also replacing initrd.img to mount /system rw (and break OTA).
Fairly sure these are my unaltered files so there are other options.
1. You could add a su.d script into /su/su.d to do what you need
2. I added a script that mounts files from /su/vendor/ over /system so - /su/vendor/etc/init.sh would be /system/etc/init.sh (not sure if it's there by default - if you add the path to /su/systemfiles.txt it will be)
ok thank you.
Related
Ok, this is how to root the 2.2 OTA:
1. Download THIS file
2. Unzip "Root.zip" to your C:/SDK_Tools/Platform-Tools/ directory
3. Double click "Root.bat"
4. You should now have the # sign in Command Prompt
5. Download THIS File THIS file and THIS
7. Mount usb storage
8. copy ESPRIMG.zip and update.zip that you downloaded to the root of your sdcard
9. Unmount usb storage
10. Unzip "eng.zip" to yous platform-tools directory and click eng-prep.bat
11. Type:
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
exit
adb reboot bootloader
11. Press Power when you see the fastboot screen, then press volume up when prompted on the device
12. Reboot into recovery, click apply: update.zip from /sdcard
13. Flash the rom of your chioce!
Your welcome
Thank NBetcher for this method!
It's great that we can root the offcial OTA this way, which is my more quickly than the one that requires goldcard and bunches of other stuffs. However, I know it's a bit too much but is it possible that we can have the rooted official Froyo version that we can flash anytime? Sometimes, I need a stable ROM but flashing the official version and then root it takes too much time. Just show me the way and I will try to do it myself if you don't have time. Thanks in advance
bearshare said:
It's great that we can root the offcial OTA this way, which is my more quickly than the one that requires goldcard and bunches of other stuffs. However, I know it's a bit too much but is it possible that we can have the rooted official Froyo version that we can flash anytime? Sometimes, I need a stable ROM but flashing the official version and then root it takes too much time. Just show me the way and I will try to do it myself if you don't have time. Thanks in advance
Click to expand...
Click to collapse
Just install NB_Mod or CR_Mod, thats exactly what you are asking for
Whoareyou said:
Just install NB_Mod or CR_Mod, thats exactly what you are asking for
Click to expand...
Click to collapse
The OTA was released later and it's newer (update3 I think). I am just curious and want to play with is for a while. If there's no major difference among those, then I will use those Mod versions. Thanks.
bearshare said:
The OTA was released later and it's newer (update3 I think). I am just curious and want to play with is for a while. If there's no major difference among those, then I will use those Mod versions. Thanks.
Click to expand...
Click to collapse
Someone posted a rooted official OTA but the link no longer works. I managed to grab it while it was available and it works very well, I even flashed Dark Tremor's a2sd to gain way more memory. This is my daily ROM now. This was the post that contained the link: http://forum.xda-developers.com/showthread.php?t=1022518
Fuzi0719 said:
Someone posted a rooted official OTA but the link no longer works. I managed to grab it while it was available and it works very well, I even flashed Dark Tremor's a2sd to gain way more memory. This is my daily ROM now. This was the post that contained the link: http://forum.xda-developers.com/showthread.php?t=1022518
Click to expand...
Click to collapse
Thanks man, but the link is down. If no one cares about it anymore then I skip it.
11. Press Volume Up when prompted on the device... this is the step thats confusing me. I have done everything as said with no errors , root.bat and eng-prep but nowhere have i recieved a prompt to press volume up? and will the prompt be on my phone or on cmd?
Balem said:
11. Press Volume Up when prompted on the device... this is the step thats confusing me. I have done everything as said with no errors , root.bat and eng-prep but nowhere have i recieved a prompt to press volume up? and will the prompt be on my phone or on cmd?
Click to expand...
Click to collapse
I messed up the .bat file, ill look in to it, but the prompt will be on your phone....i will revise the thread
Ok so I have tried to move the appropriate file to the specified directory but it doesn't exist?
I dont have a "C:/SDK_Tools/Platform-Tools/" directory. And I just installed android sdk. Do I need a different one?
Am I missing something here?
EyeAndroid said:
Ok so I have tried to move the appropriate file to the specified directory but it doesn't exist?
I dont have a "C:/SDK_Tools/Platform-Tools/" directory. And I just installed android sdk. Do I need a different one?
Am I missing something here?
Click to expand...
Click to collapse
The files need to be unzipped to the Platform-Tools folder in the android sdk directory. Look in the folder that the android sdk is installed in and you will find the platform-tools forlder.
Has this actually worked for anyone? Not getting anything telling me to press volume up. also do you do all of these steps with the phone on and booted?
I'm working on fixing the .bat right now
Sent from my NookColor using XDA Premium App
Ok, try that
Does this flash a recovery?
Clock or amonRa?
Sent from my PG86100 using XDA Premium App
Bump?
Sent from my PG86100 using XDA Premium App
jshealton said:
The files need to be unzipped to the Platform-Tools folder in the android sdk directory. Look in the folder that the android sdk is installed in and you will find the platform-tools forlder.
Click to expand...
Click to collapse
Ok Ill try that. Also do I need to have 2.2 sdk installed?
mine keeps telling me SU not found /// help
alemanandrew said:
mine keeps telling me SU not found /// help
Click to expand...
Click to collapse
Just don't type sun if you already have the "#" prompt
Sent from my NookColor using XDA Premium App
this method does not work.
It does work, just 1 typo
This Method DOES Work!
there is just one little typo that stops it's functionality. You need a space between the [chmod 04755] and [*]. It should be:
chmod 04755 *
Thanks Whoareyou!
Whoareyou said:
Ok, this is how to root the 2.2 OTA:
1. Download THIS file
2. Unzip "Root.zip" to your C:/SDK_Tools/Platform-Tools/ directory
3. Double click "Root.bat"
4. You should now have the # sign in Command Prompt
5. Download THIS File THIS file and THIS
7. Mount usb storage
8. copy ESPRIMG.zip and update.zip that you downloaded to the root of your sdcard
9. Unmount usb storage
10. Unzip "eng.zip" to yous platform-tools directory and click eng-prep.bat
11. Type:
cd /data/local
chmod 04755*
/data/local/flash_image misc /data/local/mtd0.img
exit
adb reboot bootloader
11. Press Power when you see the fastboot screen, then press volume up when prompted on the device
12. Reboot into recovery, click apply: update.zip from /sdcard
13. Flash the rom of your chioce!
Your welcome
Thank NBetcher for this method!
Click to expand...
Click to collapse
For this to work you will need to be rooted with twrp installed.
This is for people who are on the stock rom or a rom without init.d support.
1. Download the wp_mod.ko file from @flar2's thread http://forum.xda-developers.com/showthread.php?t=2701816
and copy it over to your SD card (either internal or external)
2. Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
13. profit
is this like being s-off, without being actually s-off
Not entirely, you will be able to make changes to system files while booted but you won't be able to flash fastboot zips like s-off
Or you could flash this kernel.... http://forum.xda-developers.com/showthread.php?t=2705074
And yes it does work on stock
What abt using SdFix app from google play store..??
Sent from my HTC D816w using XDA Premium 4 mobile app
silver2706 said:
What abt using SdFix app from google play store..??
Sent from my HTC D816w using XDA Premium 4 mobile app
Click to expand...
Click to collapse
that will only work to repair writing to SD CARD. This fix is for writing to the system.
Personally... If you can get s off.. I would do so. Makes life easier in the long run.
-》Sent from my mind to your screen.
insmod /system/lib/modules/wp_mod.ko failed [File exists]
Wht does it mean..?
Will it work in my HTC One M7?
system r/w on a htc one developer edition
graffixnyc said:
For this to work you will need to be rooted with twrp installed.
This is for people who are on the stock rom or a rom without init.d support.
1. Download the wp_mod.ko file from @flar2's thread http://forum.xda-developers.com/showthread.php?t=2701816
and copy it over to your SD card (either internal or external)
2. Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
13. profit
Click to expand...
Click to collapse
HI, I have an HTC One m8 developer edition
Phone details and software levels.
Model HTC One M8
Android 4.4.2
HTC sense 6.0
Software 1.54.1540.9
HTC SDK API level 6.17
I have being trying to set the r/w on system but with no success. I have followed instructions in several items in XDA and none of these have worked. I tried your method, but when finally I reboot and run root explorer I still see the folders mounted as r/o..
the .ko file is in the correct directory and install-recovery.sh is correctly modified.
Any help/assistance would be appreciated.
Unable to write system files in HTC One M7
graffixnyc said:
For this to work you will need to be rooted with twrp installed.
This is for people who are on the stock rom or a rom without init.d support.
1. Download the wp_mod.ko file from @flar2's thread http://forum.xda-developers.com/showthread.php?t=2701816
and copy it over to your SD card (either internal or external)
2. Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
13. profit
Click to expand...
Click to collapse
I too can't write system files in HTC One M7 after updating to sense 6 ROM. Will this procedure cure problem in M7? Thanks in advance
ghani.911 said:
I too can't write system files in HTC One M7 after updating to sense 6 ROM. Will this procedure cure problem in M7? Thanks in advance
Click to expand...
Click to collapse
First off, please don't quote the whole top post when its a long guide like this. I know its the default to quote the post when you reply. So just delete it, before you submit your post. We don't need the thread cluttered up with multiple reposts of what is already in the top post.
The mod makes very specific changes to the kernel, so I would say there is most likely no way in heck this will work on an M7, and might even damage it.
redpoint73 said:
First off, please don't quote the whole top post when its a long guide like this. I know its the default to quote the post when you reply. So just delete it, before you submit your post. We don't need the thread cluttered up with multiple reposts of what is already in the top post.
The mod makes very specific changes to the kernel, so I would say there is most likely no way in heck this will work on an M7, and might even damage it.
Click to expand...
Click to collapse
Ok... Sorry and thanks
HTC M8 and rw fix
Still unable to get this to work,I followed your detailed instructions and wp_mod.ko is in correct directory with correct permission and install-recovery.sh is modified correctly.
However after final rebott (several in fact) /system is still r/o
I took a TRWP backup before I started so I restored and followed your instructions again , still same result, should this work immediately or will it take several reboots before it is operative? Other discussions on this and other sites indicate the latter.
Phone details and software levels.
Model HTC One M8 developer
Android 4.4.2
HTC sense 6.0
Software 1.54.1540.9
HTC SDK API level 6.17
Any assistance or suggestions would be appreciated
Which file do I use on T-Mobile rooted One M8:
1. Sense 4.4.3 (2.22 base):
wp_mod.ko
2. Sense 4.4.2:
wp_mod.ko
3. GPE 4.4.2:
wp_mod.ko
Sn8kbordin said:
Which file do I use on T-Mobile rooted One M8:
Click to expand...
Click to collapse
Whichever Sense file corresponds to your Android build in Settings>About>Software.
If you are on the stock ROM, I'm guessing 4.4.2, since I do not believe 4.4.3 has rolled out to T-Mobile yet.
As usual, I would make a nandroid before flashing anything.
redpoint73 said:
Whichever Sense file corresponds to your Android build in Settings>About>Software.
If you are on the stock ROM, I'm guessing 4.4.2, since I do not believe 4.4.3 has rolled out to T-Mobile yet.
As usual, I would make a nandroid before flashing anything.
Click to expand...
Click to collapse
Thank you. I only needed to fix apps' write access to the SD card. Here's what I did if anyone wants to do so http://forum.xda-developers.com/showpost.php?p=54696085&postcount=13
Thank you sooo much!! used this method on my desire 816 and it worked like a charm:laugh::laugh: now i dont have restart apps like adway, sd card fix..every time i reboot
hey all worked fine until i tried to open terminal
typing :
su
insmod /system/lib/modules/wp_mod.ko
then it says in terminal "execution error occurred "
any ideas? i am sure i followed the steps
JellyTooth said:
hey all worked fine until i tried to open terminal
typing :
su
insmod /system/lib/modules/wp_mod.ko
then it says in terminal "execution error occurred "
any ideas? i am sure i followed the steps
Click to expand...
Click to collapse
I get the same thing or exec failure
One max
rgolnazarian said:
I get the same thing or exec failure
Click to expand...
Click to collapse
Me the same, on HTC One Max
(Exec format error)
plz help
thanx
I take no credit for this but I figured I'd share it credit goes to @xdabbeb from this thread. http://forum.xda-developers.com/showthread.php?t=2467302 and credit goes to @markfm for the shortcut.
But I do take the credit in packaging it into a flashable zip
Here you go I made it easy with a flashable zip ( please read and follow the instructions)
Just flash the zip
Reboot
And you're good to go
If you get an error code when trying to enter the hidden menu then do the next step otherwise you're good)
Using root browser or similar app go into system/app and find the hiddenmenu.apk and click on it and click install
In terminal emulator type "su" then type "hiddenmenu" without the quotes of course and you're in
Here's the zip: https://mega.co.nz/#!r1RnTJBK!opW5B3y4sIOUBg21DuCMXpO4vD8f5frGfer-xBKa0-U
To get back the knock on feature if you've lost it once your in the hidden menu click on HW Device Test then click on Touch Test and in there near the bottom you'll see Touch Firmware Upgrade click that and then click OK wait about 15 seconds and you're set
If you like my work please hit thanks
deleted
Does this app not bring up the same Option? I'm just wondering? Anything different from this method? https://play.google.com/store/apps/details?id=org.freespirit.hms
Worked perfectly!!!! Thank you!
Robshr said:
I take no credit for this but I figured I'd share it credit goes to @xdabbeb from this thread. http://forum.xda-developers.com/showthread.php?t=2467302 and credit goes to @markfm for the shortcut.
But I do take the credit in packaging it into a flashable zip
First download the hidden menu apk from xdabbeb's thread from above and using root browser or a similar app manually paste it into system/app and set the permissions to rw-r-r
The using root browser create a file and put this command in the file by typing in the following-
am start -a android.intent.action.Main -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
Hit save them put the file you just created in /system/bin and set the permissions to rwxr-xr-x and save
Then all you have to do is launch terminal emulator and type in the following
su and hit enter
hiddenmenu and hit enter
That's it hidden menu will then launch
Then back in terminal emulator exit out
Here you go I made it even easier with a flashable zip ( please read and follow the instructions)
Just flash the zip
Reboot
And you're good to go
If you get an error code when trying to enter the hidden menu then do the next step otherwise you're good)
Using root browser or similar app go into system/app and find the hiddenmenu.apk and click on it and click install
In terminal emulator type "su" then type "hiddenmenu" without the quotes of course and you're in
Here's the zip - https://www.dropbox.com/s/qrtzez95437t6n2/hidden menu.zip?dl=0
To get back the knock on feature if you've lost it once your in the hidden menu click on HW Device Test then click on Touch Test and in there near the bottom you'll see Touch Firmware Upgrade click that and then click OK wait about 15 seconds and you're set
Click to expand...
Click to collapse
Sorry, but I'm unclear on the highlighted text about creating a file...what do I name the file?
MIKESTONY said:
Sorry, but I'm unclear on the highlighted text about creating a file...what do I name the file?
Click to expand...
Click to collapse
You name it hiddenmenu but just do it the easy way and flash my zip file it does it all for you
Robshr said:
You name it hiddenmenu but just do it the easy way and flash my zip file it does it all for you
Click to expand...
Click to collapse
Sweet. If I already did this:
First download the hidden menu apk from xdabbeb's thread from above and using root browser or a similar app manually paste it into system/app and set the permissions to rw-r-r
Click to expand...
Click to collapse
then flashing your .zip will just override what I have done already?
MIKESTONY said:
Sweet. If I already did this:
then flashing your .zip will just override what I have done already?
Click to expand...
Click to collapse
Yes
Worked like a charm, thank you very much :thumbup:
Robshr said:
I take no credit for this but I figured I'd share it credit goes to @xdabbeb from this thread. http://forum.xda-developers.com/showthread.php?t=2467302 and credit goes to @markfm for the shortcut.
But I do take the credit in packaging it into a flashable zip
First download the hidden menu apk from xdabbeb's thread from above and using root browser or a similar app manually paste it into system/app and set the permissions to rw-r-r
The using root browser create a file and name it hiddenmenu then put this command in the file by typing in the following-
am start -a android.intent.action.Main -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
Hit save them put the file you just created in /system/bin and set the permissions to rwxr-xr-x and save
Then all you have to do is launch terminal emulator and type in the following
su and hit enter
hiddenmenu and hit enter
That's it hidden menu will then launch
Then back in terminal emulator exit out
Here you go I made it even easier with a flashable zip ( please read and follow the instructions)
Just flash the zip
Reboot
And you're good to go
If you get an error code when trying to enter the hidden menu then do the next step otherwise you're good)
Using root browser or similar app go into system/app and find the hiddenmenu.apk and click on it and click install
In terminal emulator type "su" then type "hiddenmenu" without the quotes of course and you're in
Here's the zip - https://www.dropbox.com/s/qrtzez95437t6n2/hidden menu.zip?dl=0
To get back the knock on feature if you've lost it once your in the hidden menu click on HW Device Test then click on Touch Test and in there near the bottom you'll see Touch Firmware Upgrade click that and then click OK wait about 15 seconds and you're set
Click to expand...
Click to collapse
Worked for me!
Don't worry about the manual install method just use the flashable zip
Do I need to change permissions? Its not installing
Edit I changed permissions and it didn't help.
mwebb34 said:
Do I need to change permissions? Its not installing
Click to expand...
Click to collapse
If you're using the zip it should be installed after you flash it
You can check after flashing it by going into system/apps and find the hidden menu apk and make sure it's permissions are rw-r-r
Its rw-r-r its not installing.
---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------
Deleted
mwebb34 said:
Its rw-r-r its not installing.
Click to expand...
Click to collapse
When you flash it are you getting an error and if so what's the error message
Also you are flashing it in recovery right
Robshr said:
When you flash it are you getting an error and if so what's the error message
Click to expand...
Click to collapse
Not getting any errors, when I click install apk it just says app not installed. I first flashed the zip, then I went to root explorer and tried to install the apk I got 'X App Not Installed' after that I wanted to see if terminal would see the hidden menu apk, I typed su in terminal hit enter gave su permission, then typed hiddenmenu without the quotes, was a no go. It being a system app I figured it might see it I had my doubts also.
This is what I get in the terminal app
mwebb34 said:
This is what I get in the terminal app
Click to expand...
Click to collapse
I see on your keyboard it says vanir which is an aosp ROM which this is for Verizon stock ROMs only aosp ROMs won't work
Robshr said:
I see on your keyboard it says vanir which is an aosp ROM which this is for Verizon stock ROMs only aosp ROMs won't work
Click to expand...
Click to collapse
OK, I gotcha thanks man.
I got the hidden menu working, I'm on stock now.
UPDATED 2016-08-12 I HIGHLY RECOMMEND A BETTER METHOD FOUND HERE:
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
FEWER CHANCES OF ERROR :laugh:
UPDATED 2016-08-09 TO INCLUDE 32 BIT DIRECTIONS MANY THANKS TO @ireMaN FOR INPUT
THIS IS MODIFIED NOW FOR BOTH 32 AND 64 BIT!
THIS IS ALSO ONLY FOR HDD INSTALLATIONS
Fellow Remixers:
As many have found out, version 3 of RemixOS doesn't allow changes to the system. This is because instead of a system.img it now uses a system.sfs. For most of us there is no advantage to this, and it makes it impossible to perform even simple mods to the build.prop.
So we must convert that pesky system.sfs to a system.img and substitute a modified initrd.img.
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it. EDIT 2016-08-03: WORKS FOR 3.0.102 ALSO
EDIT: 2016-08-09 WORKS FOR 3.0.103 ALSO
Here it goes:
ALL OF THIS IS DONE FROM WINDOWS. From File Explorer, navigate to your partition with RemixOS folder. Note the drive letter; mine was d:
1 Open the RemixOS folder on that drive; you should see a system.sfs file.
2 First you need to download the correct (32 or 64) modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
3 Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_(32 or 64)_rw_3.0.101.img
4 Copy that file into the RemixOS folder on the drive where you installed Remix.
5 Open the RemixOS folder; you should see both the original initrd.img and the new initrd_(32 or 64)_rw_3.0.101.img
6 Rename the initrd.img to oldinitrd.img to save it in case you need it
7 Rename the initrd_(32 or 64)_rw_3.0.101.img to initrd.img
8 Next convert that system.sfs file to a system.img file
9 Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
10 Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip. (EDIT: You may need 7zip to extract it)
11 Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
12 Open a command window by using shift&right mouse button and selecting the Open command window here
13 Assuming that your RemixOS folder is on drive c: type unsquashfs.exe -d c:\temp c:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for c: (EDIT: Do not change the -d as it is part of the command)
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
14 Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
15 Copy it into the RemixOS folder
16 Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
17 Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
NOTE: TO TAKE OTA UPDATE YOU NEED TO DO THE Following FROM WINDOWS:
A In File Explorer, navigate to the RemixOS folder
B Find and rename the initrd.img to initrd_(32 or 64)_rw_3.0.101.img depending on your version
C Find and delete system.img
D Rename oldsystem.sfs to system.sfs
E Reboot ti RemixOS and download the update and select the Reboot option.
F After the OTA is installed and you are at the desktop you need to repeat steps 6 through 17 above
Any suggestions to make this easier please let me know. Please PM me and I will answer your questions.
Thanks a lot... Will try and reply you soon.... But I'm sure it works
Sent from my S II using XDA Labs
changing orientation
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
lollyjay said:
Fellow Remixers:
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it.
Here it goes:
All of this is done from Windows. From File Explorer, navigate to your partition with RemixOS directory. Note the drive letter; mine was d:
Open the RemixOS folder on that drive; you should see a system.sfs file.
First you need to download a modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_rw_3.0.101.img
Copy that file into the RemixOS folder on the drive where you installed Remix.
Open the RemixOS folder; you should see both the original initrd.img and the new initrd_rw_3.0.101.img
Rename the initrd.img to oldinitrd.img to save it in case you need it
Rename the initrd_rw_3.0.101.img to initrd.img
Next convert that system.sfs file to a system.img file
Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip.
Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
Open a command window by using shift&right mouse button and selecting the Open command window here
Assuming that your RemixOS folder is on drive d: type
unsquashfs.exe -d d:\temp d:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for d:
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
Copy it into the RemixOS folder
Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
Rename the initrd_rw_3.0.101.img to initrd.img
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse
Some Question
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help
rajnallan said:
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
Click to expand...
Click to collapse
Thank you for the compliment. My knowledge does not extend to that area; perhaps @HypoTurtle can help?
asuduakali said:
Any suggestions to make this easier please let me know.
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help
Click to expand...
Click to collapse
I wish I knew...
Edit: I suspect that they locked access to speed up the system by disabling disk i/o
lollyjay said:
I wish I knew...
Edit: I suspect that they locked access to speed up the system by disabling disk i/o
Click to expand...
Click to collapse
I succeed to do it using stickmount after i copied these imgs .
just check usbstorage folder with file explorer ( i'm using ES)
lollyjay said:
Fellow Remixers:
There has been so much interest in this that I have tried to write a guide. I hope it is accurate, but I encourage feedback to improve it.
Here it goes:
All of this is done from Windows. From File Explorer, navigate to your partition with RemixOS directory. Note the drive letter; mine was d:
Open the RemixOS folder on that drive; you should see a system.sfs file.
First you need to download a modified initrd.img from here:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkTm5raUZRZXl4NkE
Use File Explorer to navigate to the Downloads folder; you should see a file named initrd_rw_3.0.101.img
Copy that file into the RemixOS folder on the drive where you installed Remix.
Open the RemixOS folder; you should see both the original initrd.img and the new initrd_rw_3.0.101.img
Rename the initrd.img to oldinitrd.img to save it in case you need it
Rename the initrd_rw_3.0.101.img to initrd.img
Next convert that system.sfs file to a system.img file
Using your web browser, download and install RMXTools from http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Then in File Explorer, navigate to Downloads folder and extract the RMXTools zip.
Then navigate to the newly created RMXTools folder and navigate to the bin64 folder
Open a command window by using shift&right mouse button and selecting the Open command window here
Assuming that your RemixOS folder is on drive d: type
unsquashfs.exe -d d:\temp d:\RemixOS\system.sfs
If your drive letter is e: for example, you would substitute e: for d:
You should see it writing blocks for a few seconds
This should create a new system.img file on drive d: in folder temp
Now you need to navigate again to the drive with the RemixOS folder. You should see your newly created system.img in the temp folder
Copy it into the RemixOS folder
Now open the RemixOS folder; you should see your new system.img alongside the original system.sfs.
Rename the system.sfs to oldsystem.sfs to keep it in case you need it again
Rename the initrd_rw_3.0.101.img to initrd.img
OK now time to reboot into Remix
You should now have writable system
Hope this helps
If it works for you please hit the "thanks" and if you're REALLY happy then I can always use coffee money
Any suggestions to make this easier please let me know.
Click to expand...
Click to collapse
Tried it now. Worked like a charm. killing the thanks button
Everything working fine... I'd clean install replacing both files, thank you very much, and also i installed SuperSU for better root magement and besides.. with this one StickMount works perfectly...
doing this Adaway can work?
dark8899 said:
doing this Adaway can work?
Click to expand...
Click to collapse
Yes, of course
asuduakali said:
how to mount HDD Partition like previous version? is there any trick to show it again?
Hope Anyone Here Can Help
Click to expand...
Click to collapse
Try changing ro.remixos.scan_all_parts=false
rajnallan said:
Thanks a lot. Not only you are a very helpful person , you have lots of patience. Thanks for all your inputs and guidance. I checked using CPU-Z and find all sensors are working including rotation sensor. I alos see that the new build.prop has the line ro.remixos.box is set to flase. But still my surface pro does not auto rotate to portrait mode. I am also not able to force it into portrait mode. Can you help please?
Thanks
Click to expand...
Click to collapse
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
xSilverLight said:
Everything working fine... I'd clean install replacing both files, thank you very much, and also i installed SuperSU for better root magement and besides.. with this one StickMount works perfectly...
Click to expand...
Click to collapse
Yea, stickmount seems to need the [updated] superSU su binary; so either system.img rw or systemless root would do [also the build.prop edit mentioned above might be an alternative to stickmount but editing build.prop needs system rw anyway].
Addendum; if anyone is using my 32bit su.img; you need to make a /su/xbin_bind folder and reboot before SuperSU will update the binary
HypoTurtle said:
Yea, stickmount seems to need the [updated] superSU su binary; so either system.img rw or systemless root would do [also the build.prop edit mentioned above might be an alternative to stickmount but editing build.prop needs system rw anyway].
Addendum; if anyone is using my 32bit su.img; you need to make a /su/xbin_bind folder and reboot before SuperSU will update the binary
Click to expand...
Click to collapse
Exactly, also I'll try that you mention and thanks for the info..
And also.. thanks for all your contributions
HypoTurtle said:
Try changing ro.remixos.scan_all_parts=false
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
IT is already showing ro.remixos.has_adjust_display =false
The latest remix OS based on Marshmallow carries all these changes.
Click to expand...
Click to collapse
Thanks. Now I can use stick mount and access my hdd.
hhaiwzz said:
Thanks. Now I can use stick mount and access my hdd.
Click to expand...
Click to collapse
You're very welcome my pleasure
I'm at a loss as to how to get this working on a USB install on my system. Are people using hard drive installs or USB flash drive ones? I'm using a 64gb Sandisk Extreme flash drive.
1st off - using the Windows tool that comes in the installer from Jide's website (downloaded file I have is Remix_OS_for_PC_Android_M_64bit_B2016072603.zip ) to "install" RemixOS onto the flash drive works flawlessly but after that I'm unable to see any other volumes other than one called REMIX_OS which is not a system volume. I've formatted the flash drive 4 times already and redid the installation each time. Each time the install is perfectly bootable but in terms of being able to boot into windows and brows the RemixOS folder to modify system files there is no change, I'm unable to see all volumes on the flash drive. I only see one volume while in windows and that one appears to be an SD CARD (It's called REMIX_OS and only has an Android and Lost folder in it) rather than the system volume for Android.
If I insert the flash drive into my Macbook I'm able to see two volumes, the volume called REMIX_OS I referred to earlier and another volume called REMIXOSSYS which does have the system files in it (with the initrd.img and system.sfs that need to be replaced) . .
So after using the RMXTools on my Windows machine to create a system.img file (which ends up ballooning to 2.6gb, is that the right size?) and downloading the requisite initrd_rw_3.0.101.img and renaming both original files on the REMIXOSSYS volume (using my Mac) and copying the new ones onto the flash drive volume I'm able to boot into RemixOS on my PC normally.
Everything works fine until I actually try to edit build prop as a test at which point I'm unable to. The system itself operates just fine otherwise but system still isn't writeable.
I'm not quite sure why others are easily able to do everything they need to do on their PC's using windows explorer to modify the system files and I'm not. I tried it on both my home and work PCs and the result is the same. Nonetheless I'm thinking that since all that is supposed to be required to make system writeable is to replace the initrd.img and system.sfs with the modified initrd.img and a system.img file then it really shouldn't matter if I do it using a Mac or a PC . . i'm confused at this point lol.
Any thoughts?
rajnallan said:
HypoTurtle said:
Try changing ro.remixos.scan_all_parts=false
Haven't found what's forcing landscape; yet... maybe see what changing ro.remixos.has_adjust_display=false does; but it's probably nothing
IT is already showing ro.remixos.has_adjust_display =false
The latest remix OS based on Marshmallow carries all these changes.
Click to expand...
Click to collapse
Yea; I said change it. i.e. to true
Click to expand...
Click to collapse
muzzy996 said:
I'm at a loss as to how to get this working on a USB install on my system. Are people using hard drive installs or USB flash drive ones? I'm using a 64gb Sandisk Extreme flash drive.
1st off - using the Windows tool that comes in the installer from Jide's website (downloaded file I have is Remix_OS_for_PC_Android_M_64bit_B2016072603.zip ) to "install" RemixOS onto the flash drive works flawlessly but after that I'm unable to see any other volumes other than one called REMIX_OS which is not a system volume. I've formatted the flash drive 4 times already and redid the installation each time. Each time the install is perfectly bootable but in terms of being able to boot into windows and brows the RemixOS folder to modify system files there is no change, I'm unable to see all volumes on the flash drive. I only see one volume while in windows and that one appears to be an SD CARD (It's called REMIX_OS and only has an Android and Lost folder in it) rather than the system volume for Android.
If I insert the flash drive into my Macbook I'm able to see two volumes, the volume called REMIX_OS I referred to earlier and another volume called REMIXOSSYS which does have the system files in it (with the initrd.img and system.sfs that need to be replaced) . .
So after using the RMXTools on my Windows machine to create a system.img file (which ends up ballooning to 2.6gb, is that the right size?) and downloading the requisite initrd_rw_3.0.101.img and renaming both original files on the REMIXOSSYS volume (using my Mac) and copying the new ones onto the flash drive volume I'm able to boot into RemixOS on my PC normally.
Everything works fine until I actually try to edit build prop as a test at which point I'm unable to. The system itself operates just fine otherwise but system still isn't writeable.
I'm not quite sure why others are easily able to do everything they need to do on their PC's using windows explorer to modify the system files and I'm not. I tried it on both my home and work PCs and the result is the same. Nonetheless I'm thinking that since all that is supposed to be required to make system writeable is to replace the initrd.img and system.sfs with the modified initrd.img and a system.img file then it really shouldn't matter if I do it using a Mac or a PC . . i'm confused at this point lol.
Any thoughts?
Click to expand...
Click to collapse
Method works only for hdd installations afaik
wow thanks for this, now since we have an open system, can we install xposed framework?
How can I unpack recovery.img? I am running linux on my PC.
Well I found a way, so thought that I should share it with all.
You need dsixda's Android Kitchen and recovery.img of any phone you want to unpack.
I am running a linux pc.
You can look for installation steps in following thread:
https://forum.xda-developers.com/showthread.php?t=633246
Open a terminal.
Type the following command to go into the directory of android kitchen
For example, I have to go in this path using terminal
/home/augustoandro/Android/android-kitchen , then I type
cd /home/augustoandro/Android/android-kitchen
Click to expand...
Click to collapse
After that
./menu
Click to expand...
Click to collapse
Now choose ADVANCED OPTIONS by entering the no. in front of the option.
Now, select "unpack/repack boot.img" option in the same way.
Now, enter "a".
A folder would be created in the android kitchen folder. In my case, /home/augustoandro/Android/android-kitchen/boot-img-64647470
Copy and paste the recovery.img file in the new folder.
Go back to the terminal and press enter.
The recovery.img file would be unpacked in the same folder.
You can look for it using the file explorer.
Hit thanks button if found useful