Could anyone guide me how to get my hands on tools that can do what rmxtools basically does but on linux that is extract .sfs to .img then unpack and repack img and root the img, rmxtools 1.8fix doesn't seem to be working on win 7 64bit and win8.1 64 bit.
TundraLK520 said:
Could anyone guide me how to get my hands on tools that can do what rmxtools basically does but on linux that is extract .sfs to .img then unpack and repack img and root the img, rmxtools 1.8fix doesn't seem to be working on win 7 64bit and win8.1 64 bit.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=e-3vkDMADS0
https://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
bg260 said:
https://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296;)
Click to expand...
Click to collapse
I had tried android_img_repack_tools, also in xda but it didn't help. I can unpack and extract img files easily in linux but the repacking of img files doesn't work. Squashfs tools can extract and repack but the file doesn't work when trying to boot and install remix os. The size of the new sfs file is smaller as compared to the original sfs file even though files are being added. So it could be that the compression is not recognised.
TundraLK520 said:
I had tried android_img_repack_tools, also in xda but it didn't help. I can unpack and extract img files easily in linux but the repacking of img files doesn't work. Squashfs tools can extract and repack but the file doesn't work when trying to boot and install remix os. The size of the new sfs file is smaller as compared to the original sfs file even though files are being added. So it could be that the compression is not recognised.
Click to expand...
Click to collapse
When you say "doesn't work" what do you mean? Are you seeing the grub menu? Which USB tool are you using?
I use that method when I modify PhoenixOS, I just use. It's the same thing RMX Tools uses. I think you may have different problems.
Use SuperR. It works. Make sure to set as raw image.
bg260 said:
When you say "doesn't work" what do you mean? Are you seeing the grub menu? Which USB tool are you using?
I use that method when I modify PhoenixOS, I just use. It's the same thing RMX Tools uses. I think you may have different problems.
Use SuperR. It works. Make sure to set as raw image.
Click to expand...
Click to collapse
No grub, instead an error i forgot what it was. I'll give SuperR a try.
TundraLK520 said:
No grub, instead an error i forgot what it was. I'll give SuperR a try.
Click to expand...
Click to collapse
I just published this how-to with furiusisomount.
https://forum.xda-developers.com/android/development/linux-easily-manipulate-img-t3533342
Basically you can make changes without unpacking.
bg260 said:
I just published this how-to with furiusisomount.
https://forum.xda-developers.com/android/development/linux-easily-manipulate-img-t3533342
Basically you can make changes without unpacking.
Click to expand...
Click to collapse
Furiousisomount is great. Thanks.
Related
Delete
I don't know, where did I get it, so it may be outdated or something.
mkyaffs for windows
Here is mkyaffs2 exe file compiled for Windows using Cygwin.
Archive contains makeyaffs and unyaffs files and needed dll's.
P.S. I tryed to use that compiled "mkyaffs"-file to create system.img and img-file really was created, but when I tryed to unpack that system.img (using unyaffs that works normally) I just got "OK"-message from unyaffs and nothing more! No one folder was created! So I think my compiled mkyaffs doesn't work properly. It's creating corrupted img's. :silly:
So the most reliable and right way to pack folders into img's is use mkyaffs on Linux or virtual machine (with booted Linux of course).
P.S.S. I found tool named Yaffey, but I don't know how to get it create system.img
Kyonex said:
Here is mkyaffs2 exe file compiled for Windows using Cygwin.
Archive contains makeyaffs and unyaffs files and needed dll's.
P.S. I tryed to use that compiled "mkyaffs"-file to create system.img and img-file really was created, but when I tryed to unpack that system.img (using unyaffs that works normally) I just got "OK"-message from unyaffs and nothing more! No one folder was created! So I think my compiled mkyaffs doesn't work properly. It's creating corrupted img's. :silly:
So the most reliable and right way to pack folders into img's is use mkyaffs on Linux or virtual machine (with booted Linux of course).
P.S.S. I found tool named Yaffey, but I don't know how to get it create system.img
Click to expand...
Click to collapse
Thank you so much! It's what software I look for exactly.
Description: Utility (hereinafter - the kitchen) to make changes to the firmware image for the Lenovo K900.
Operating System Requirements: Any Linux-like system (I recommend Ubuntu), any digit. For correct working kitchen must be installed packges: p7zip, p7zip-full, jdk, jre, python, ia32-libs.
Features: Removing the preinstalled Chinese software from the VibeROM firmwares; other firmware - manual; deodexing firmware; adding ROOT rights in firmware; editing build.prop; installing Google apps (* not verified), repacking the system.img.gz image.
Instructions for use:
- unpack the archive to any folder;
- Run the kitchen with console command ./kitchen.sh and enter the root password (required for file operations);
- Copy the file system.img or system.img.gz in a folder /in/;
- Enter 1 if throwing system.img.gz image archive folder in /in/, or go to step 2 if the folder /in/ drop files system.img;
- Type 2 to mount the image, while in the kitchen wearing the phrase "System: unmounted" will change to "System: mounted". The system is mounted in a folder /mount/;
Then simply describe the menu items:
3 - removes Chinese preinstalled software according file cn-apps in /scripts/ folder;
4 - "easier" firmware by deleting unnecessary files, animation off; applies mods - Record video to MP4, boot animation changed to "clipped " (you can change your folder /scripts/mod/);
5 - deodexing firmware (it takes quite a long time , up to 10 min);
6 - adding ROOT rights (used SuperSU 1.93). If you want to use a different version, you can replace the files in the /scripts/root/;
7 - editing build.prop file by using gedit;
8 - Set the Google apps light with a minimum set of software, you can further install more right already from Google Market (not tested);
9 - edited image packaging system system.img.gz. Ready to pick up the file from the folder /out/;
10 - unmount mounted image. Performed at the end of all operations with an editable manner;
0 - unpack inb firmware;
x - exit.
Download link:
http://forum.xda-developers.com/devdb/project/dl/?id=5359
Download mirror:
https://drive.google.com/folderview?id=0Bz3X7ZuowQimM3c0ZFV2QlZMR2c&usp=sharing
XDA:DevDB Information
Lenovo K900 kitchen, Tool/Utility for the Lenovo K900
Contributors
xxx-man-by
Version Information
Status: Testing
Stable Release Date: 2014-02-17
Created 2014-02-19
Last Updated 2014-06-07
What a great job！:good:
Amazing
Now its time to cook some ROM's
Lenovo K900 kitchen 1.21 beta
Released new version 1.21 beta
Whats new:
- Added support for firmware format INB (unpacking only);
- SuperSU binaries updated to version 1.93;
- Added support for complex tools with Android 4.3 (deodex, zipalign, optipng). Work is not very stable.
great, I hv prepared ubuntu and hv started cooking
Released new version 1.23
Whats new:
- Changed the script for implementation Root rights firmware (to fully support Android 4.3)
Just asking...
no kitchen for Windows7?
pjsplayez said:
Just asking...
no kitchen for Windows7?
Click to expand...
Click to collapse
No. Only for Linux-like OS, because Windows cannot work with images, mounting, rights etc...
Thank you i try it and install root Good Job
Just ask
xxx-man-by.. why not just "inb" file in "sdfuse" folder ?!. thanks before
Thank you, I am being to buy that device ^_^
Dual boot
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
help XXX-Man
i think the link is not working anymore.
REupload please
pjsplayez said:
help XXX-Man
i think the link is not working anymore.
REupload please
Click to expand...
Click to collapse
Ok. I`ll upload to the mirror. Please wait. DONE.
pjsplayez said:
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
Click to expand...
Click to collapse
if you need linux just for cooking, dont install it to harddrive.. just throwit on some usb drive and run it live..
use pendrivelinux or yumi to make live linux on usb.
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
sev7en said:
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
Click to expand...
Click to collapse
I do not understand what you mean.
xxx-man-by said:
I do not understand what you mean.
Click to expand...
Click to collapse
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
sev7en said:
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
Click to expand...
Click to collapse
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
xxx-man-by said:
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
Click to expand...
Click to collapse
thank you for getting me back sooner, with your unique Kitchen we are able to manage that files as well to repack them but when done how we get the final package to flash?
thanks once again for that
I'm using Windows 8, and i need to Repack the system files to System.img (i extracted it by ext4)
Thanks!!!
amitams said:
I'm using Windows 8, and i need to Repack the system files to System.img (i extracted it by ext4)
Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1588461
After some googling, it seems like you should consider using a linux virtual machine on windows... I'm not aware of any tool on windows.
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?
@MikeChannon, please delete this.
Deleted topic because I don't think about giving more support.
Use @SuperR. kitchen.
Reserved
ohhh thanks bro!!! great job
Enviado desde mi POCOPHONE F1 mediante Tapatalk
I want to use Linux. How to use?
Virus??!!
Why my windows 10 security center scaned the virus??!!
ClassiCTR said:
I want to use Linux. How to use?
Click to expand...
Click to collapse
Sorry, it's a Windows tool.
568060545 said:
Why my windows 10 security center scaned the virus??!!
Click to expand...
Click to collapse
Because batch file it's converted to .exe and thats why. Don't worry. It's safe.
Version updated to 1.1
Best performance
https://www.androidfilehost.com/?fid=6006931924117938149
JamFlux said:
Version updated to 1.1
Best performance
https://www.androidfilehost.com/?fid=6006931924117938149
Click to expand...
Click to collapse
hi bro, first thank you for the mighty work you do
i need to repack my rom to other format not to original format
zemzmi said:
hi bro, first thank you for the mighty work you do
i need to repack my rom to other format not to original format
Click to expand...
Click to collapse
Go to 01-Project folder, then temp folder and rename for the format you need: system.img, system.new.dat or system.new.dat.br, then restart application and recover the project.
JamFlux said:
Go to 01-Project folder, then temp folder and rename for the format you need: system.img, system.new.dat or system.new.dat.br, then restart application and recover the project.
Click to expand...
Click to collapse
thanks and good work :good:
possible virus detected
JamFlux said:
Because batch file it's converted to .exe and thats why. Don't worry. It's safe.
Click to expand...
Click to collapse
So then, Why is SUR.exe needed if Sur.bat works ok without it?
Bro, virustotal detects 8/69 threats of SUR.exe file:
https://www.virustotal.com/gui/file/68f8708f5f156caef86535cb132e82527eb08ead3facaf3f09c10ab28618670c/behavior/VirusTotal%20Jujubox
Behaviour of this file does these filesystem actions:
Code:
Processes Tree
2584 - factura.exe
148 - C:\Windows\system32\cmd /c C:\Users\<USER>\AppData\Local\Temp\D751.tmp\D752.bat C:\Users\<USER>\Downloads\factura.exe
2812 - mode con: cols=72 lines=13
WTH is factura.exe?
Similarly, SUR_v1.1u.7z is 13/51 detected by Virustotal.
najabi said:
So then, Why is SUR.exe needed if Sur.bat works ok without it?
Bro, virustotal detects 8/69 threats of SUR.exe file:
https://www.virustotal.com/gui/file/68f8708f5f156caef86535cb132e82527eb08ead3facaf3f09c10ab28618670c/behavior/VirusTotal%20Jujubox
Behaviour of this file does these filesystem actions:
Code:
Processes Tree
2584 - factura.exe
148 - C:\Windows\system32\cmd /c C:\Users\<USER>\AppData\Local\Temp\D751.tmp\D752.bat C:\Users\<USER>\Downloads\factura.exe
2812 - mode con: cols=72 lines=13
WTH is factura.exe?
Similarly, SUR_v1.1u.7z is 13/51 detected by Virustotal.
Click to expand...
Click to collapse
Hi @najabi
I used a tool to compile .bat to .exe, may be its a false positive. I use that program because it can add administrative privileges. But now I put administrative privileges to .bat inside. Just use .bat from here: https://github.com/jamflux/SUR/raw/master/SUR.bat
Can't open?
JamFlux said:
Hi @najabi
I used a tool to compile .bat to .exe, may be its a false positive. I use that program because it can add administrative privileges. But now I put administrative privileges to .bat inside. Just use .bat from here: https://github.com/jamflux/SUR/raw/master/SUR.bat
Click to expand...
Click to collapse
Hi JamFlux,
I tried to unpack a vendor .zip with the utility using the .bat but I got an error anyway.
I think it's best to use scripting commands than .exe binaries when possible, they are easier to spot and analyse. You can use administrative command promt aswell. Which tool do you use to make executables from .bat files? Is it from reputable sources?
najabi said:
Hi JamFlux,
I tried to unpack a vendor .zip with the utility using the .bat but I got an error anyway.
I think it's best to use scripting commands than .exe binaries when possible, they are easier to spot and analyse. You can use administrative command promt aswell. Which tool do you use to make executables from .bat files? Is it from reputable sources?
Click to expand...
Click to collapse
Hi
I'm using this tool:
https://bat-to-exe-converter.uptodown.com/windows
But now I'm using command promt inside .bat
Hope you can unpack vendor.img
Best regards
JamFlux said:
Hi
I'm using this tool:
https://bat-to-exe-converter.uptodown.com/windows
But now I'm using command promt inside .bat
Hope you can unpack vendor.img
Best regards
Click to expand...
Click to collapse
In my opinion, I don't think it's a reputable tool, the developer's webpage doesn't work, and uptodown is not exactly a trusted source.
We must be extra careful these days as they put virus everywhere in executables.
That SUR.exe file is detected as infected by several engines, I think you should consider removing it from the tool.
najabi said:
In my opinion, I don't think it's a reputable tool, the developer's webpage doesn't work, and uptodown is not exactly a trusted source.
We must be extra careful these days as they put virus everywhere in executables.
That SUR.exe file is detected as infected by several engines, I think you should consider removing it from the tool.
Click to expand...
Click to collapse
I remove totally the executable in new version. Thanks.
New version 1.2 supporting deodexing from android 8.0 to android Q.
Download: https://www.androidfilehost.com/?fid=6006931924117945116
@JamFlux mate i have one question. Can I also unpack, edit (removing or adding apps, e.g.) and repack MIUI ROMs? Thx!
Sent from my [device_name] using XDA-Developers Legacy app