Hi, I want to execute (then install) an personalized Android ROM on my PC, I tried to change the distribution of Android x86 but the ISO file reconstructed (by Nero) is not read (An error tells me that no files were found for the start) and are not able to open (for modding) the file in SFS inside the original ISO. So I tried modding the files of Windroy Project and the result was more than excellent! (I have modded files of Windroy in C drive) but now I do not know how to make these files "installed" as indipendent OS, it is possible, and if so, how? Thanks for the answers
UP!!
I would like to run the. exe file in an base operating system (also CMD) that start the .exe by start, exist?
---blacksoul--- said:
Hi, I want to execute (then install) an personalized Android ROM on my PC, I tried to change the distribution of Android x86 but the ISO file reconstructed (by Nero) is not read (An error tells me that no files were found for the start) and are not able to open (for modding) the file in SFS inside the original ISO. So I tried modding the files of Windroy Project and the result was more than excellent! (I have modded files of Windroy in C drive) but now I do not know how to make these files "installed" as indipendent OS, it is possible, and if so, how? Thanks for the answers
Click to expand...
Click to collapse
try in here
http://forum.xda-developers.com/showthread.php?t=1272270
hawaja said:
try in here
http://forum.xda-developers.com/showthread.php?t=1272270
Click to expand...
Click to collapse
My problem is not knowing how modding a ROM, but to bring a ROM on PC and open that file type, which requires a separate procedure.
Related
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
HERE IS A GUIDE FOR YOU ALL YOU CAN CREATE YOUR OWN ROM BY THIS METHOD.I AM NOT RESPONSIBLE FOR BRICKED DEVICES.
Click to expand...
Click to collapse
Requirement to make a custom rom
*JAVA JDK installed on your SYSTEM
*WIN XP/ 7/8/8.1.
*package given in download section
Who is this kitchen for ?
Those who are brand new to
creating custom ROMs and
want an easy place to start
learning
Those who just want to modify
shipped ROMs or someone
else's custom ROMs to their
liking
Those who are confused by all
those scripts and complex
commands required for
building and extracting
This is NOT a tool to
automatically turn you into a
full-fledged ROM developer.
ROM development normally
involves work from the ground
up and involves time , research
and patience .
Click to expand...
Click to collapse
PRESS THANKS IF YOU LIKE MY WORK..
Kitchen setup
setting up dsixda kitchen
1.download all the three link and unzip kitchen.rar and cywin package.
2.open cywin_package then open folder now, you can see 3 icons, a read-
me,a setup, and a folder. Choose
the setup. Here you will choose
install from local directory. Next,
navigate to the the folder of
extraction of cygwin and choose
the folder cygwin_packages inside
the cygwin extraction folder. Wait
for some time. Then, you will come
across a list of file. Click the 2-
circle-arrows,untill, it displays
“install”
after the procedure is complete,
run the batch file cygwin.bat . Now, minimise
it and copy kitchen folder,
keep it in some location where you have installed your cygwin package open home/ajay-pc(in my case this is administrator name of my pc)kitchen
now, open the batch file window
and type
cd c:\kitchen
wait for some time and then when
the location the changed, type
./menu
Click to expand...
Click to collapse
press thanks if you like my work
GUIDE
now minimize the batch file and extract official rom there you will find system.img then extract it using magic iso or flash
the official stock rom using odin the take a nandroid backup u will get system.rfs.tar in your sd card extract it using magic iso then make a folder in called rom and open it. again create a folder called system and copy all data from system.rfs.tar which u have extracted(do drag and dropping).
Now copy meta-inf of any stock rom and copy and kernel to rom folder.
Now you will get two folder and one file in your rom folder zip the folder content and copy the file where you have installed cygwin/home/ajay/kitchen/original update folder.
now open command shell which you have minimized 1st create working folder then add root permission,deodex your rom.
and at last press 99 to build your rom..
note-if it ask you to change updater script to update script change it but dont forget to change it back to updater script.now you will get your rom in output folder copy it to your sd card flash it if error occur unzip the zip file and delete meta-inf and boot.img and again copy meta-inf of any rom and kernel to it and zip it..again flash the rom..
PRESS THANKS IF YOU LIKE MY WORK
DOWNLOADS
Downloads
Link for cygwin click here :good:link for kitchen click here :good:link for magic iso click here :good:
Link for official firmware click here :good:
PRESS THANKS IF YOU LIKE MY WORK
CREDIT
DSIXDA for Android Kitchen
Samsung for this awesome device
ME for this Guide
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting
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?