Updating SU binary always fails? - Remix OS for PC

I moved a pre-rooted system.sfs to my remix drive and tried to run SuperSU but when i try to update the binary it always fails. Any idea why? I can provide whatever info is needed

fix error update binary superSU
Note: change system.sfs to system.img, don't use system.sfs

tuong1008 said:
Note: change system.sfs to system.img, don't use system.sfs
Click to expand...
Click to collapse
how? do i rename the file? reinstall the os?

Quote100 said:
how? do i rename the file? reinstall the os?
Click to expand...
Click to collapse
RMXtools [emoji4]

original Thread Here : http://forum.xda-developers.com/remi...a-img-t3308158
Remix OS Root Method with windows For 2.0 or Below Version
Video Tutorial : https://www.youtube.com/watch?v=JV6vZqGQ4sE
For Downloading RMX Tool v1.5 Download Here : Owner Link | External Link
Remix OS Root Method with windows For 2.0.101 and Above Version
Video tutorial : https://www.youtube.com/watch?v=IFGzmc81ta0
Ref :http://forum.xda-developers.com/remix/remix-os/how-to-root-remix-os-windows-video-t3311406
Thanks to kabeerkhan2016 for Video, and imadlatch for RMX Tool

my remix os is system.img but still same can't update binary su, remix os 64 bit new version.. i using rmx tool 1.7 fix version

Su Binary Installation Failed !!
I have installed RemixOS 3.0.207 64bit and rooted using RMXtools 1.8 Fix. But SuperSu shows Su Binary needs updated. When I click update, installation fails. I have tried converting system.sfs into system.img it gets same error. Help Me !!

Related

Lenovo K900 kitchen 1.23

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

[Q] recovery systemUi.apk

i want to find suitable systemUi.apk file for my system ..... my device is an ( Chinese ) 7 inch table (company name : artcom) running with android 4.0.4 with processor A13 .
i searched online for it`s rom and i found this links :
http://www.4shared.com/get/4qQbjIjBc...-20130418.html
and a user tried to install it on the same device and it`s worked fine with some problem in touch screen .
so i wont to install it what i need is to get only the systemUi.apk from .img file
i tired to unzip it but says file is courrpted .
touristgump said:
i want to find suitable systemUi.apk file for my system ..... my device is an ( Chinese ) 7 inch table (company name : artcom) running with android 4.0.4 with processor A13 .
i searched online for it`s rom and i found this links :
http://www.4shared.com/get/4qQbjIjBc...-20130418.html
and a user tried to install it on the same device and it`s worked fine with some problem in touch screen .
so i wont to install it what i need is to get only the systemUi.apk from .img file
i tired to unzip it but says file is courrpted .
Click to expand...
Click to collapse
Extract system.IMG from your downloaded ROM
After extracting system.IMG install Linux reader (free software google it)
Using Linux reader open IMG file and extract system ui apk and paste it to system/app via any root file manager ....
Else use adb fast boot method to flash system.IMG in fast boot mode ...(this method will unroot your device )
All the best ?
Sent from my x604 using Tapatalk
The-Immortal said:
Extract system.IMG from your downloaded ROM
After extracting system.IMG install Linux reader (free software google it)
Using Linux reader open IMG file and extract system ui apk and paste it to system/app via any root file manager ....
Else use adb fast boot method to flash system.IMG in fast boot mode ...(this method will unroot your device )
All the best ?
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
i followed this tutorial :
http://forum.xda-developers.com/showthread.php?t=2294909
but when i import the img file into ext4 image unpacked. he says couldnt read the file
is there a pre step before use it to get system.img from .img file then use it to extract system.img
any help please

Manual Updating Remix OS

If any of you have install Remix OS as a dual boot or in the internal storage then Remix OS can be updated with ease. Please don't delete your data.img file during this process.
1. Copy the new *.iso files in the package and overwrite the older one.
2. Generate the bootable usb drive drive with included usb tool and copy all the content from the usb to your Remix drive. Overwrite files if necessary.
3. Reboot your pc/laptop/tablet to remix os. It will take some time to update.
4. Voila! Remix os has been updated with battery icon and other small fixes.
What about pre-rooted system.img ? I use a rooted remix os and if I use this method, will it affect the system.img?
TheBasterd said:
What about pre-rooted system.img ? I use a rooted remix os and if I use this method, will it affect the system.img?
Click to expand...
Click to collapse
will require manual re-rooting....by whichever method you acquired?
but...who has a copy of the updated iso?

Remix OS Latest Update 2.0.202 have prerooted feature now :) cool!!

The latest update of the Remix OS 2.0.202 now has pre-rooted feature. no need to install the super user or any other root apps, simply by changing the file init.img with the one that has a R/W system and we are now rooted( cause the original init.img from jide still has R/O system in it), nice feature Jide and TY for great OS
oh ya, for who is not having this update, it is in unstable version. tap 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS ( stable enough for me)
note: keep and backup the original files init.img as will be needed for OTA update
because if the original file is missing or replaced OTA update will fail..
enjoy it..
Cannot find init.img file that has a R/W system
This is really cool and I have just updated my Remix OS installation with the latest update (2.0.202) but I don't know where to find the init.img file that has a R/W system in order to have root access. Thanks for your help...
stathious said:
This is really cool and I have just updated my Remix OS installation with the latest update (2.0.202) but I don't know where to find the init.img file that has a R/W system in order to have root access. Thanks for your help...
Click to expand...
Click to collapse
u can download init file that has R/W system 32 bit or 64 bit , here
can you share the download link with files of 2.0.202 version, because when i click reboot and install button it goes straight to Windows and does nothing !?
Thanks in advance
Where i put the initrd.img on my remix os drive ? Prerooted features means that I can install application that needs root or not ?
tasadar said:
can you share the download link with files of 2.0.202 version, because when i click reboot and install button it goes straight to Windows and does nothing !?
Thanks in advance
Click to expand...
Click to collapse
use stock beta version Remix OS u can download update 2.0.202 only from stock unmodified rom
Almercer said:
Where i put the initrd.img on my remix os drive ? Prerooted features means that I can install application that needs root or not ?
Click to expand...
Click to collapse
put init file in where u install remix os in RemixOS folder, yes pre-rooted means it already rooted from the 1st u update remix to version 2.0.202, and if u want u can update root feature with superSU directly from Remix after booting from playstore,
I am not getting root even after adding the intrd.img. Yes, I am using 2.0.202.
Root behaviour is same as previous build for me i.e. Alt&F1 has root; system doesn't.
@arts821 any chance you are using 32bit?
I have root anyway; using my system-less root ramdisk.img; just curious on how the stock su via settings works...
Also changing to a rw initrd shouldn't be needed for root to work as in OP, but is needed to alter ant system files; but note mounting system as rw will break OTA and require restoring an unaltered version.
No root access with this
Hmm..maybe not all system have this feature, try install supersu from play store to make sure as u can see in my screenshot the root feature icon is setting icon, and yes I using 32bit remix, and wipe all my data.img(fresh install)
It seems only 32bit is rooted, which sucks because I like using all my RAM, I have 8gb ram, lol.
I could not install the .202 although I am using stock version. After click reboot and install it just reboots to old version. Please give download link with sysmtem file of the new version !?
Ps: I am using it on z3740 cpu tablet
can someone upload version 2.0.202? cause my laptop processor won't boot any previous version and this version provides a special fix for it. Compress system from img to sfs using RMXTools, kernel and initrd files and archive them, I will replace them in my iso.
Thanks in advance..
I guess it's not possible do to change the file in Remix Mini since root would be need to change that file...isn't it?
arts821 said:
u can download init file that has R/W system 32 bit or 64 bit , here
Click to expand...
Click to collapse
dumb question, will placing that file in a 2.0.102 build give root?
dkryder said:
dumb question, will placing that file in a 2.0.102 build give root?
Click to expand...
Click to collapse
Yes, and no. If you are on 32bit your good to go but 64bit is a no go.
HypoTurtle said:
Root behaviour is same as previous build for me i.e. Alt&F1 has root; system doesn't.
@arts821 any chance you are using 32bit?
I have root anyway; using my system-less root ramdisk.img; just curious on how the stock su via settings works...
Also changing to a rw initrd shouldn't be needed for root to work as in OP, but is needed to alter ant system files; but note mounting system as rw will break OTA and require restoring an unaltered version.
Click to expand...
Click to collapse
Would you mind sharing a link to your ramdisk.IMG? Please??
electrikjesus said:
Would you mind sharing a link to your ramdisk.IMG? Please??
Click to expand...
Click to collapse
Are you on 64 or 32bit?
I have 64bit remix and 32bit phoenix done; will need a copy of 32bit Remix to do one for that (the phoenix one might work as is)
64 is at the top here
i'm on 32bit, replaced initrd.img, installed super su, but no root for me, i tap 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS but no root after reboot
EDIT: FIXED i'm on dual boot, entered from windows, deleted data.img and system. img, copied again system.img from remixos iso, tapped 5 time Remix OS version in setting/about to make available option in the 3rd unstable version remix OS, tested in terminal su command and now it's all ok!

Remix OS System.img repacker tool for Linux

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.

Categories

Resources