Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.
Wuby986 said:
hey there!!! i can give you a couple of suggestion, even if i don't get if you are only extracting or also editing and repacking since i don't see any repack code.. anyway.. first of all you definitely should use -R in yoour chown code.. this means recursive.. so you don't have to do it for every folder, subfolder and so on!! do a chown -r for sys and you're done with it.
then another thing.. i personally use a script that will handle all this by itself, i put it in the file explorer script folder and so you can access it from everywhere just right-clicking on the file you want to mount.. it will need to edit path for pass it as variable, but it's easy.. at least once you know how to
so this is my script:
Code:
#!/bin/bash
CWD=(pwd)
simg2img [email protected] img.img; mkdir /tmp/system; mate-terminal -x sudo mount -t auto -o loop img.img /tmp/system; mate-terminal -x sudo chown -R login:login /tmp/system
just to explain, you see simg2img because i work with sparse img ( from samsung) that must be converted to regular img before get mounted, so i have the simg2img binary compiled and moved into /usr/local/bin path to access it from any path.. you will need to do the same or to remove that part if you don't need it.
also you must change mate-terminal to plain terminal since you're on unity i can see
then move the script to /home/your_login/.nautilus/script (again because you're on unity using nautilus i think) check if it has the exec bit enbled from permission and then enjoy..
oh another thing.. in case you need to copy keeping the permissions and ownership, so that you don't ahve to fix all that later you simply don't set the last part of the script - the chown part, since you can access the subfolders and files anyway and for ex. use the "cp -a /tmp/system/app /your_desired_path to work on it.
Click to expand...
Click to collapse
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.
Cleopatra Bianchi said:
Thank you very much for your suggestions
I have to admit that I am a newbie/noob ... particularly on Linux (I have installed Ubuntu OS just a week ago ... I come from the planet Windows). I have tried "android_img_repack_tools-android-6.0.1_r3_x64.tar.gz" ... but simg2img doesn't works (I am not able to convert system.img in raw). I'm trying to mod a system.img Mediatek Marshmallow.
Kindest Regards.
Click to expand...
Click to collapse
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?
Wuby986 said:
i hano NO idea about mediatek devices, you should ask in the corresponding fora, but most likely you don't need simg 2 img since that's not a sparse img, so you could be able to mount it strait away.. or at least try first without converting it.
what's the error you're getting in terminal?
Click to expand...
Click to collapse
This is the error in terminal :
Cleopatra Bianchi said:
This is the error in terminal :
Click to expand...
Click to collapse
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack
Wuby986 said:
yeah then is definitely not a sparse img.. maybe a regular img or other kinda of..
you should search for the mtk device forum for this info.. or better yet maybe the @dsixda kitchen has a conversion binary for it, so you can see which is and use it instead of the simg2img.. this kitchen is not anymore updated, so you cannot use it for everything like repack or root, but should work for unpack
Click to expand...
Click to collapse
Ok ... I'll do it. Thank you very much for your suggestions.
Happy Easter
Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)
---------- Post added at 08:59 AM ---------- Previous post was at 08:59 AM ----------
Cleopatra Bianchi said:
Hi to all. I am a newbie ... but I try to do all my best
Above all please make a directory under /mnt (I called the directory "MyMount1"); "mylogin" represents your login name.
Open the terminal and type the next commands:
-sudo mkdir /mnt/MyMount1
-sudo chown mylogin:mylogin /mnt/MyMount1
-copy system.img & paste it into MyMount1 (computer/mnt/MyMount1)
-cd /
-cd mnt
-cd MyMount1
-mkdir sys/ && sudo mount -t ext4 -o loop system.img sys/
-sudo chown mylogin:mylogin sys (without this command you will not be able to copy and modify anything)
-cd sys
-sudo chown mylogin:mylogin addon.d (without this command you will not be able to copy and modify anything)
-then copy addon.d & paste it into Ubuntu Desktop (now you can make any changes you want)
-then delete addon.d into /mnt/MyMount1/sys
-copy addon.d (into Ubuntu Desktop) & paste it into /mnt/MyMount1/sys
-then apply the same command to every folder inside system.img (/mnt/MyMount1/sys) and repeat the procedure (copy it into Ubuntu Desktop, make changes and paste it into /mnt/MyMount1/sys).
The following screenshot will help you better understand all the steps :
Before "sudo chown mylogin:mylogin sys" command :
After "sudo chown mylogin:mylogin sys" command :
Before "sudo chown mylogin:mylogin addon.d" command :
After "sudo chown mylogin:mylogin addon.d" command :
That's all ... for now
XDA:DevDB Information
System.img, ROM for all devices (see above for details)
Contributors
Cleopatra Bianchi
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2016-03-24
Last Updated 2016-03-24
Click to expand...
Click to collapse
pro tip use -R to make chown reclusive and include all the subfolders
sudo chown login:login -R (folder in sys)
Related
YOUR PHONE WILL STILL WORK DOING THIS.. ITS ALMOST LIKE RUNNING AN APP ON YOUR PHONE
I got most of my information from this site here.. I only rewrote it and shared to get it working on our cdma hero.
http://www.androidfanatic.com/component/fireboard/?func=view&id=1615&catid=9
I also use files from different sources and combined them to work with our phone.
As of right now this method seems to only work with DarchDroid aosp rom. Not any htc sense roms.
Also make a ext partition and dont use apps2sd, darchdroid is set by default not to use it, only if enabled in spare parts app
If you want to try and get both debian and apps2sd to work.. Try this guide here http://forum.xda-developers.com/showthread.php?t=509943.
First download is the files you will need OTHER then the debian.img
The main files
This one will be a big download. It contains the most important part.
The debian.img from here
Once download, open it up and only take the "debian.img" out of it.
This will put a 1.4gb file on your sdcard used for running debian not including the other files it uses to install and run it (they are very small). If you have a small sdcard and want the image smaller or want to enlarge the .img for more room. Use this tutorial here.
TO CHANGE FILE SIZE OF debian.img
Im going to be using adb on the computer. Much easy then typing commands into the phone terminal.
Put the all the files into a folder on your sdcard named debian.
First downloaded files and the debian.img from the 2nd download.
/sdcard/debian
Next you will need to make the directory it uses. For some reason its not creating it on the install
Code:
adb shell
su
mkdir /data/local/mnt
Next you need to install the debian.
Code:
cd /sdcard/debian
sh installer.sh
reboot
Then it should work after this. When your phone boots back up you need to install this APK here. This is what will actually run the desktop "lxde" or whatever you choose to install after this.
*****View attachment vnc.apk*****
To install put it in your android-sdk/tools folder.. where ever it may be installed and type...
Code:
adb remount
adb push vnc.apk /system/app
Or put it on your sdcard and install it using Astro or any other app installing app
Then run the debian you just installed by doing this
Code:
adb shell
cd /sdcard/debian
sh bootdeb
Then you need to run this script only once.
It will look like this
localhost:/#
type
Code:
cd /scripts/
sh onetime.sh
When it ask for password. Just type "android"
Open the vnc app
Fill out the information like so...
connection: just dont touch
Nickname: can leave blank
Password: android
Address: LocalHost
Port: 5901
Color: I used 24-bit, you can pick whatever you want. Its changeable from within the running desktop
Then click on Connect at the top. And everything should work.
TO USE TOUCH SCREEN.. DO THIS
click our menu button on our phone.
then click "Scaling" and select 1.1..
Then push the trackball 1 time and touch screen mouse will work
To run without using your computer. Download a terminal from the market and type this...
Code:
su
cd /sdcard/debian
sh bootdeb
Then open up your vnc app and press connect.
To use icewm.. more simple looking desktop. Runs smoother
First you need icewm while running bootdeb
Code:
localhost:/# apt-get install icewm
Then to switch between ice and ldxe do this in terminal on your phone. This is actually easy do to using the trackball
Code:
localhost:/# nano /root/.vnc/xstartup
Scroll down to lxsession and delete it.. then type xterm
Save changes by pressing track ball once and the letter o. Then press enter. Exit out by pressing the track ball once again and type the letter x.
Then connect using VNC.apk and it will load the new desktop.
Delete xterm and type lxsession to change back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
omfg thank you so much. I'll try this as soon as I get home <33333
edit: I assume this fixes the permission errors I was getting on the thread I created about running the full de on the hero.
Thanks dude, thats awesome! I will have to take a look at it when I get home as well
Linux Rules!
good one jus debian on a hero classic
Jus FTW! Now I wonder if we can start doing the same for other linux distros.
Re: Install debian and use lxde
This is pretty geek-chic, I love it.
Actually, I do have a question about it. Anyway to boot and use Deb without VNC?
It sounds like it's an ARM compiled, headless Debian install running in the background, which is why you need VNC to access it, correct?
Is it network aware? How fast is it?
no way...RAD!!!
I have tried to install following instructions using terminal on he phone......seems like I get through the install.sh ok then after reboot try to run the bootdeb and it says not found.? also I get the vnc fails when trying to connect?
I am sure i am doing something wrong but not sure what.
any suggestions?
I forgot to say THANKS Jus!
i get "bootdeb not found" when i know i copied it over.. i'm going to try again.
alright, copied the files again the same thing. i'm interested in this! it's just something else i can do my iphone friends can't lol
snip3rm00n said:
Actually, I do have a question about it. Anyway to boot and use Deb without VNC?
Click to expand...
Click to collapse
yes, if you have ssh running on it, im sure you could ssh into the system. the reason for vnc is to have a gui.
hurrah. this is pretty slick, if i had a larger sd card id do this
thedudejdog said:
i get "bootdeb not found" when i know i copied it over.. i'm going to try again.
alright, copied the files again the same thing. i'm interested in this! it's just something else i can do my iphone friends can't lol
Click to expand...
Click to collapse
I get the same thing. I know its there, I checked.
Code:
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb shell
# cd /sdcard/debian
cd /sdcard/debian
# ls
ls
unionfs
bootdeb
fsrw
installer.sh
mountonly
debian.tar.bz2
# bootdeb
bootdeb
bootdeb: not found
#
This is the exact same issue I used to have, and I've never been able to get it to work. I read someplace that I should try "sh bootdeb", but here's the output on that:
Code:
# sh bootdeb
sh bootdeb
uid=0(root) gid=0(root)
[H[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't change root directory to /data/local/mnt: No such file or directory
Shutting down Debian........
#
Any ideas?
UPDATES / EDITS:
I also tried:
Code:
#su bootdeb
gave no output and seemed to go fine, but upon trying to connect through vnc, said vnc connection failed. So the I tried:
Code:
#./bootdeb
and got "permission denied". So THEN I tried:
Code:
#su ./bootdeb
And again seemed like everything was cool, but VNC still said connection failed. I've tried connecting using both LocalHost and 127.0.0.1, still nada.
how come the graphics look so ****ty? i mean tp2 users can run ubuntu and it looks perfect.
thedudejdog said:
i get "bootdeb not found" when i know i copied it over.. i'm going to try again.
alright, copied the files again the same thing. i'm interested in this! it's just something else i can do my iphone friends can't lol
Click to expand...
Click to collapse
Try to type
sh bootdeb
And make sure you
cd /sdcard/debian
drummingfool said:
I get the same thing. I know its there, I checked.
Code:
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb shell
# cd /sdcard/debian
cd /sdcard/debian
# ls
ls
unionfs
bootdeb
fsrw
installer.sh
mountonly
debian.tar.bz2
# bootdeb
bootdeb
bootdeb: not found
#
This is the exact same issue I used to have, and I've never been able to get it to work. I read someplace that I should try "sh bootdeb", but here's the output on that:
Code:
# sh bootdeb
sh bootdeb
uid=0(root) gid=0(root)
[H[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't change root directory to /data/local/mnt: No such file or directory
Shutting down Debian........
#
Any ideas?
UPDATES / EDITS:
I also tried:
Code:
#su bootdeb
gave no output and seemed to go fine, but upon trying to connect through vnc, said vnc connection failed. So the I tried:
Code:
#./bootdeb
and got "permission denied". So THEN I tried:
Code:
#su ./bootdeb
And again seemed like everything was cool, but VNC still said connection failed. I've tried connecting using both LocalHost and 127.0.0.1, still nada.
Click to expand...
Click to collapse
Same problem i had... You have to do
mkdir /data/local/mnt
and then cd /sdcard/debian and run it again
Also to everyone
Read the instructions again.. I added
how to use touch screen and how to fix the mounting problem
fixxxer2008 said:
how come the graphics look so ****ty? i mean tp2 users can run ubuntu and it looks perfect.
Click to expand...
Click to collapse
The graphics are also pretty nice.. I used 256 color for the first screen shot. If you use 24bit it cleans it up really nicely.
I did everything per new instructions and all was good up to the sh bootdeb part, I get a readout of a bunch of crap then: chroot: cant execute '/bin/bash': No such file or directory.
But i am closer than last time and getting anxious
beerock said:
I did everything per new instructions and all was good up to the sh bootdeb part, I get a readout of a bunch of crap then: chroot: cant execute '/bin/bash': No such file or directory.
But i am closer than last time and getting anxious
Click to expand...
Click to collapse
Do
adb shell
cd /sdcard/debian
sh installer.sh
sh bootdeb
cd /scripts/
sh onetime.sh
if it ask for password.. just type android
Credit to sofauxboho for performing dumps.
Partition Dump
http://gititbit.ch/sk4g2 - partition dump
Code:
bml1 256 KB contains boot.bin (262144 bytes), Primary Boot Loader (low-level hardware initialization)
bml2 256 KB contains PIT file first 512 bytes
bml3 10240 KB /dev/block/stl3 /efs
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml6 5120 KB param.lfs /mnt/.lfs j4fs
bml7 7680 KB contains zImage and initramfs
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
bml9 293376 KB factoryfs.rfs ( /system RFS Partition) /dev/block/stl9
bml10 137216 KB dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
bml11 35840 KB cache.rfs ( /cache RFS Partition) /dev/block/stl11
bml12 12800 KB modem.bin
EDIT: It has come to my attention that the Super One Click works, no need for a script.
More Mirrors
http://gititbit.ch/sk41 - Sidekick 4G system dump
http://gititbit.ch/sk4g1 - Sidekick 4G Info Dump
dev.txt
devblock.txt
efs.txt
mount.txt
partitions.txt
proc.txt
Kernel + Platform Source
http://gititbit.ch/sk4g5 - SGH-T839_OpenSource.zip
Now for custom roms...
SK4G development chat can be found at irc.freenode.net #sk4g
hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.
Use winrar to extract the .rar then place the extracted folder onto the sdcard.
dasmoover said:
Use winrar to extract the .rar then place the extracted folder onto the sdcard.
Click to expand...
Click to collapse
ok, think i did that, but am still getting 'operation not permitted'..... perhaps i'll hold off and see if someone else has success with it?
Hmm...
Should line 14 specify the su file rather than the containing directory?
It currently reads:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/
But perhaps it should read:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/su
Updated the script in the main download.
yogi2010 said:
hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.
Click to expand...
Click to collapse
Im getting this when I try the lines too.
When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
No I was usin the old link didn't try new one yet. Still says same thing on new version
Sent From SK4G
sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
I tried the newer download. All of the chmods error because my user doesn't own those files or already have write permissions for any of them. I don't have read, write, or execute permissions for /data/local/tmp either, so I can't list or copy to that location. But, separate from that, there is no cp command, so I can't copy anything anywhere.
jarrodlombardo said:
When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.
Click to expand...
Click to collapse
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.
sofauxboho said:
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.
Click to expand...
Click to collapse
Type this into terminal right?
Actually, I whipped up a modified version of dasmoover's tool with my changes:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip that and copy the "autoroot" folder to your SD card.
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer.
Then follow dasmoover's instructions (I've cleaned them up slightlly):
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
chmod 755 /sdcard/autoroot/autoroot.sh
./sdcard/autoroot/autoroot.sh
If the sdcard is mounted as noexec, follow these steps:
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
cat > /sdcard/autoroot/autoroot.sh /data/local/tmp/autoroot.sh
chmod 755 /data/local/tmp/autoroot.sh
cd /sdcard/autoroot/
./data/local/tmp/autoroot.sh
Click to expand...
Click to collapse
All credit to dasmoover, btw! Thanks, and I hope you don't mind me modifying and repackaging your tool. Just trying to help get it working.
BTW, here are some good goodies on how this root exploit works for the technical and curious:
I'd read this one first: http://intrepidusgroup.com/insight/2010/09/android-root-source-code-looking-at-the-c-skills/
And this one second:
http://dtors.org/2010/08/25/reversing-latest-exploid-release/
How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G
I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)
Ace42 said:
How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G
Click to expand...
Click to collapse
So, the # means root. The $ means not root. The whole point of this is to get the #, which indicates a root prompt.
If it says the directory can't be found then either the command was typed incorrectly or the files are in the wrong place. The files have to be in the exact right places with the exact right names.
Download my modified version:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip it, and it should give you a folder called "autoroot". Inside that should be four files:
autoroot.sh
rageagainstthecage-arm5.bin
su
Superuser.apk
Make sure there is only a folder named "autoroot" with those four files inside. If there is another directory inside it won't work. If the names are at all different it won't work.
Copy this "autoroot" folder to the top level of your SD card. There should be other folders there like Music, DCIM, Playlists, and Android. Maybe some others. Make sure it's at the very top level, along with these other directories.
Here, take a look at my directory structure:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Yes, I'm on a Mac, but your SK and Android don't care. File locations work the same on Windows or Linux or whatever. Also, I may have some folders you don't have. That's ok.)
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer. **I forgot this part earlier! It's important.**
Then open up Terminal Emulator an your SK4G. Type:
Code:
cd /sdcard/autoroot
Then type:
Code:
ls
This should list the same four files above. If it does, you're ready to start the instructions I posted previously.
If it doesn't, type:
Then type:
Code:
ls /sdcard/
Let me know what it says.
jarrodlombardo said:
I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)
Click to expand...
Click to collapse
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
(To confirm, you can still root by using adb to manually put these files at /data/local/tmp/ For some reason, adb has rights to this location. However, the standard Terminal Emulator does not. This is only a hang-up for on-device rooting, not rooting in general.)
sofauxboho said:
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
Click to expand...
Click to collapse
I've poked around some and not found anywhere yet. :/
While browsing XDA i didn't find anything for unpacking Livesuite images so i created this THREAD.
Things you need
Allwiner kitchen
Stock Firmware
Linux image tool
Ubuntu 64 bit
Click to expand...
Click to collapse
Lets start
Step 1
Extracting and building the stock image (Windows)
Extract a10_flash_kitchen_v1.zip and look inside the directory, you'll see packer_gb and packer_ics. packer_ics is for Android ICS, so that is the one you will be using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open packer_ics and you will notice a bunch of directories and a couple of .bat scripts. We will spend a lot of time in these directories.
Extract the stock firmware you downloaded earlier, and copy the .img file into this directory. Rename the file to original.img.
Run the extract_image.bat script, and a command window will pop up while it is extracting.
The command window will output like the following, it will display Press any key to continue . . . when it is complete. Press a key to close the window.
Once the command window is closed, open the _extract directory and all of the extracted files will be there. The three following files are the ones we are interested in: RFSFAT16_BOOT_00000000000.fex (the boot partition), RFSFAT16_RECOVERY_0000000.fex (the recovery partition), RFSFAT16_SYSTEM_000000000.fex (the system partition, ext4 sparse).
NOTE and WARNING Some systems may also have a RFSFAT16_BOOTLOADER_00000.fex, which may also be required for your device to boot properly. There are some vague instructions @ this TechKnow forums post. I (the reader) will attempt to clarify and modify this page with the updated additional instructions for these devices to aid in making these instructions more universal for anyone using LiveSuit.
Click to expand...
Click to collapse
Step 2
Extracting, modifying and building partitions (Linux)
Copy your Extracted files to ubuntu
Rename the files as follows:
RFSFAT16_BOOT_00000000000.fex -> boot.img
RFSFAT16_RECOVERY_0000000.fex -> recovery.img
RFSFAT16_SYSTEM_000000000.fex -> system.fex
Click to expand...
Click to collapse
Copy the tools.tar.gz archive you downloaded earlier into the same directory.
To extract the tools, right click on the file and click Extract here.
This will extract the tools into a tools subdirectory.
Type terminal to show the terminal application. Hit enter and the terminal will appear.
Boot partition
Code:
$ cd "custom image"
$ tools/split_bootimg.pl boot.img
$ ls
Now extract the ramdisk file into a ramdisk subdirectory.
Code:
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
$ ls
You are now able to modify the files as needed.
Once you have finished modifying the file, we will rebuild the image. Run the following commands.
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-boot.img
$ ls
Recovery partition
his follows the same process as the boot partition. Execute the following commands to extract the image:
Code:
$ tools/split_bootimg.pl recovery.img
$ rm -rf ramdisk
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../recovery.img-ramdisk.gz | cpio -i
$ ls
rebuild the image with the following commands:
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel recovery.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-recovery.img
$ ls
System partition
The process for the system partition is different, because it is not bootable and because it is ext4 sparse, so it cannot be mounted straight away. Execute the following commands to convert and mount the image:
Code:
$ tools/simg2img system.fex system.img
$ mkdir system
$ sudo mount -o loop system.img system
$ cd system
$ ls
Once you are done, execute the following commands to rebuild the system image:
Code:
$ cd ../tools
$ sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
$ cd ..
$ sudo umount system
$ ls
Now switch back to the file browser and you will see many new files in your directory. The three files that you are interested in are new-boot.img, new-recovery.img, new-system.fex
Copy these to your Windows drive to the directory a10_flash_kitchen_v2/packer_ics/_input
Click to expand...
Click to collapse
Step 3
Building the new image (Windows)
Once the files are copied, jump back to Windows and rename the files as following:
new-boot.img -> root.fex
new-recovery.img -> recovery.fex
new-system.fex -> system.fex
Click to expand...
Click to collapse
http://i.imgur.com/klTA5.png/img]
Now we need to make some modifications to the image config file. Navigate to the files directory and you should see image.cfg.
[img]http://i.imgur.com/Wg6Ov.png/img]
Open this file using your text editor that supports Unix line endings. Using Notepad will break this file. Locate the two lines that reference OEM and VOEM as is highlighted below.
[img]http://i.imgur.com/YxczH.png
Comment these lines by adding a semicolon ( to the start of each line. Do not make any other modifications. Save the file once you have made the change.
http://i.imgur.com/urMMN.png/img]
Go back to the packer_ics root directory and find the create_image.bat script. It will open a console while it is creating the new image.
[img]http://i.imgur.com/X2O6l.png
Once the process is complete, you will see Press any key to continue . . . and you will have a new image called output.img.
AND JUST FLASH IT AND YOU ARE DONE
Click to expand...
Click to collapse
Credits
miniandwiki
To ME
To Everyone who helped me creating this one
do i have to use 64bit liux?? i only have a 32 bit computer?? thnx
Permission denied
Hey....
I installed Ubuntu on an external disk. But even logged at su (also tried sudo su) I dont have the permission to perform with the Linux-tool. When I click at the roo-folder, it is already set to rw permission for root.
What am I doing wrong?
Links are broken, can you kindly update them.
Links are broken Pls Upload to another host
A few days ago, I flashed a zip onto my phone that set SELinux to permissive. However, there was a problem: it deleted logd, which is essential to adb logcat. Considering I'm an Android developer, that isn't a good thing! It took me a bit to figure out how to get it back, so I'm making this guide to share with you guys to help whatever poor soul has to fix this next.
Note that these steps were designed with Linux in mind, though they might be adaptable to Cygwin/OSX with some effort.
Also, make sure you delete any SELinux permissive scripts from init.d/su.d first!
Prerequisites
The OTA or custom rom zip that your device is currently running
adb
simg2img (available in the Ubuntu software repositories)
sdat2img (available here)
Instructions
Put your OTA/custom ROM zip file in a new folder and unzip it (this example is using the Pure Nexus ZIP):
Code:
mkdir restore_logd
cp pure_nexus_hammerhead-7.0-20161025-HOMEMADE.zip restore_logd
cd restore_logd
unzip pure_nexus_hammerhead-7.0-20161025-HOMEMADE.zip
Now, look for a file named either system.new.dat or system.img.
If you have system.img, then run:
Code:
simg2img system.img system.raw.img
If you have system.new.dat AND system.transfer.list, instead run:
Code:
sdat2img.py system.transfer.list system.new.dat system.raw.img
Either way, you should now have a file named system.raw.img. Next, mount it:
Code:
mkdir system_mnt
sudo mount -t ext4 -o loop system.raw.img system_mnt
This will mount the system image onto the system_mnt folder.
Plug in your device to your computer and make sure USB debugging is enabled, then run:
Code:
adb push system_mnt/bin/logd /sdcard/logd
adb shell
You should now be in a shell connected to your device. Inside, run:
Code:
su
mount -o rw,remount /system
cp /sdcard/logd /system/bin/logd
chmod 755 /system/bin/logd
exit
This will install the logd binary and close the shell.
This next part is very important! Making sure you closed the adb shell and are still inside the directory you created, run:
Code:
ls -Z system_mnt/bin/logd
If the output looks like this:
Code:
? system_mnt/bin/logd
then you have nothing else to do. Otherwise, it might look a bit like this:
Code:
u:object_r:logd_exec:s0 system_mnt/bin/logd
Copy part before the path; in this case, it's:
Code:
u:object_r:logd_exec:s0
Then, run:
Code:
adb shell su root chcon permission /system/bin/logd
replacing permission with the string you copied.
Now you can unplug and restart your device; logd should now be fully working!
Last but not least, run:
Code:
sudo fusermount -u system_mnt
to unmount the system image from your computer.
Enjoy!
Execute command failed while replacing permission
Code:
adb shell su root chcon permission /system/bin/logd
u:object_r:logd_exec:s0
/system/bin/sh: <stdin>[1]: u:object_r:logd_exec:s0: not found
Introduction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well I was Going Through The possibilities of Termux and was extracting .Dat compression in my PC to extract some files out of system folder Then i readed in one xda thread that Termux can install Python,cmake, and all in our Android itself also seen that Python script by @xpirt on @matrixex thread for unpack repack .Dat on pc I seen that this Python script converts .dat to .img Then suddenly One idea arised in my mind Why don't I try that in my phone itself I tried and the result was just insane it worked like a charm in real. Now we want files but it is in .img extension how can we extract that then i Found This app called Zarchiver on playstore You can unpack the image now and use those files or edit them Also i found Another interesting app Android image kitchen by which you can unpack the image and make changes in the image content by import export of files but it leaves the image as it is in .img extension only can edit but can't unpack so the Zarchiver method is the best.....
This can help Rom porters and Rom developing Dev's
Plz don't forget to hit the thnx button it can appreciate someone ???
I am still a noob so i can't answer Dev's professional questions but I think Other Dev's Moderators and Contributors will help the DEv's
Special thnx to
@xpirt
@matrixex
@termuxAppDevloper
@ZArchiverAppDevloper
@aindroidImageKitchenAppDevloper
@dg28gadhavi Aka me
Guide
Files to be download:
Termux app
Termux Api app
Commands.txt
Zarchiver app
AIK app
Es file explorer
Quick text editor
Links:
TermuxApp
TermuxApiApp
Zarchiver
AikApp
EsFileexplorer
Quickest ditor
Pythonscript
Commands.txt
1. Install the given apps and download all requirements
2. Open Termux app and let it be initialize 1st
3. Copy commands from command.txt step by step
4. Download python by apt-get install python (note but follow the commands.txt commands first and go step by step)
5. Make a folder name ext in internal memory/download
6. Extract the python script zip (sdatmaster.zip) and copy it in internal memory/download/ext
7. Also copy Your system.new.dat , system.transfer.list and filecontext in internal memory/download/ext folder
8. Now Following the command.txt Type this command- termux-setup-storage
9. Now change path to directory as mentioned in command.txt- cd storage/downloads/ext
10. Now execute that python script as mentioned in commands.txt- python sdat2img.py system.transfer.list system.new.dat system.img
11. Copy the code to convert.dat to .img
12. Use Zarchiver to unpack/extract the image
13. Unpacking done enjoy
Note
Root required
And it can't extract OEM Delta OTA updates
Good Guide.
dg28gadhavi said:
Guide
Click to expand...
Click to collapse
We can also use Image Factory app to do this https://m.apkhere.com/app/crixec.app.imagefactory
For new brotli packages we need additional commands
Code:
cd /sdcard/Download/ext
pkg install brotli
brotli -d system.new.dat.br -o system.new.dat
Pack ke system.new.dat TO system.new.dat.br what do you do
Wahyu6070 said:
Pack ke system.new.dat TO system.new.dat.br what do you do
Click to expand...
Click to collapse
Try the below command to compress system.new.dat to brotli
Code:
cd <path to system.new.dat directory>
brotli system.new.dat -o system.new.dat.br
Repack system.new.img to system.new.dat
:good:
repack system.new.img to system.new.dat how do you do it
Wahyu6070 said:
:good:
repack system.new.img to system.new.dat how do you do it
Click to expand...
Click to collapse
https://github.com/xpirt/img2sdat
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
python img2simg.py system.img fail
to repack the system folder to system.img. the code that I use: python img2simg.py system.img system2.img, posted on xpirt the way it is but can't.
xpirt posts use linix instead of termux
how to use linux pc instead of android thermux and use sudo command
Wahyu6070 said:
to repack the system folder to system.img. the code that I use: python img2simg.py system.img system2.img, posted on xpirt the way it is but can't.
Click to expand...
Click to collapse
How you got system folder? Did you mounted system.img to some folder?
I rented dat to img. then I uninstall the file system.img using zarchiver, and in that folder there are build pro files, prive apps etc., and how do I change it back to img ... then to dat
Wahyu6070 said:
I rented dat to img. then I uninstall the file system.img using zarchiver, and in that folder there are build pro files, prive apps etc., and how do I change it back to img ... then to dat
Click to expand...
Click to collapse
I dont know how to do that from a folder....
But If you are using mobile you can mount it somewhere and tweak it....
Code:
mkdir /data/local/system
mount -t ext4 -o rw,noatime <system.img path> /data/local/system
You can now tweak /data/local/system folder ...
After tweaking that system folder you have to unmount /data/local/system
Code:
umount /data/local/system
img2simg system.img system_sparse.img
img2simg binary can be found in FlashFire apk lib folder for your arch...
Then you have to use img2sdat.py code.....
HemanthJabalpuri said:
I dont know how to do that from a folder....
But If you are using mobile you can mount it somewhere and tweak it....
Code:
mkdir /data/local/system
mount -t ext4 -o rw,noatime <system.img path> /data/local/system
You can now tweak /data/local/system folder ...
After tweaking that system folder you have to unmount /data/local/system
Code:
umount /data/local/system
img2simg system.img system_sparse.img
img2simg binary can be found in FlashFire apk lib folder for your arch...
In flashfire.apk / lib / exist 2 folders (armeabi-v7a and x86) and deep in the folders of the fishery format libimg2simg.so not img2simg.py do I have to change the format
Click to expand...
Click to collapse
Wahyu6070 said:
In flashfire.apk / lib / exist 2 folders (armeabi-v7a and x86) and deep in the folders of the fishery format libimg2simg.so not img2simg.py do I have to change the format
Click to expand...
Click to collapse
You have to rename it to img2simg.......
Note that img2simg and img2sdat.py are different ones.....
HemanthJabalpuri said:
I dont know how to do that from a folder....
But If you are using mobile you can mount it somewhere and tweak it....
Code:
mkdir /data/local/system
mount -t ext4 -o rw,noatime <system.img path> /data/local/system
You can now tweak /data/local/system folder ...
After tweaking that system folder you have to unmount /data/local/system
Code:
umount /data/local/system
img2simg system.img system_sparse.img
img2simg binary can be found in FlashFire apk lib folder for your arch...
Then you have to use img2sdat.py code.....
Click to expand...
Click to collapse
I think the code that is used cannot
Code:
1|[email protected]:/data/data/com.termux/files/home #
rw,noatime system.img /data/local/system <
mount: 'system.img'->'/data/local/system': No such file or directory
Wahyu6070 said:
I think the code that is used cannot
Click to expand...
Click to collapse
You need to first change working directory if you want to only use system.img as arg instead of whole path
Code:
cd <directory path to system.img>
HemanthJabalpuri said:
You need to first change working directory if you want to only use system.img as arg instead of whole path
Code:
cd <directory path to system.img>
Click to expand...
Click to collapse
Code:
ount -t ext4 -o rw,noatime <system.img path> /data/local/system <
mount: bad /etc/fstab: No such file or directory
still can't
Wahyu6070 said:
still can't
Click to expand...
Click to collapse
Your code is wrong...
Place system.img extracted from .dat file in /sdcard/Music folder and type following
Code:
su
mkdir /data/local/system
mount -t ext4 -o rw,noatime /sdcard/Music/system.img /data/local/system
Now you can go to /data/local/system and tweak it and unmount afterwards
Place img2simg binary in /sdcard/Music and
Code:
umount /data/local/system
exit
cp /sdcard/Music/img2simg $HOME
chmod +x $HOME/img2simg
cd $HOME
./img2simg /sdcard/Music/system.img /sdcard/Music/system_sparse.img
HemanthJabalpuri said:
Your code is wrong...
Place system.img extracted from .dat file in /sdcard/Music folder and type following
Code:
su
mkdir /data/local/system
mount -t ext4 -o rw,noatime /sdcard/Music/system.img /data/local/system
Now you can go to /data/local/system and tweak it and unmount afterwards
Place img2simg binary in /sdcard/Music and
Code:
cp /sdcard/Music/img2simg $HOME
chmod +x $HOME/img2simg
umount /data/local/system
cd $HOME
./img2simg /sdcard/Music/system.img /sdcard/Music/system_sparse.img
Click to expand...
Click to collapse
Code:
/system/bin/sh: su: not found
127|[email protected]:/data/data/com.termux/files/home #
d/Music/system.img /data/local/system <
[email protected]:/data/data/com.termux/files/home #
cp /sdcard/Music/img2simg $HOME
cp: //img2simg: Read-only file system
1|[email protected]:/data/data/com.termux/files/home #
chmod +x $HOME/img2simg
chmod: //img2simg: No such file or directory
1|[email protected]:/data/data/com.termux/files/home #